Customer ID algorithm is too aggressive
HI there!
I know we will never have a feature that allows us to communicate directly with the client as it is baked into the Bunny concept that the clients are always yours and we are only here to provide a service to you.
And because of that, the system automatically strips away anything that may even remotely seem like customer contact information.
However, in this instance, it is acting too aggressively to remove info vital to the proper completion of the project by thinking that it is customer contact info. Here is what appeared in the instructions for a job:
"... like in the examples of #xxxxxx and #xxxx22..."
The sample numbers were automatically removed by system. Now all I can do is take a blind stab at what the client wants instead of having sample to go by.
You may say, "Well, just contact support." A fair option. However, the job showed up at midnight my local time. By the time I got up, I had already gotten the "Client is waiting" notification. Historically, it takes hours and sometimes days to get a response.
A look into the parameters of info removal may be in order
Please sign in to leave a comment.
Hi Mark,
Thank you for reaching out to us!
We appreciate you bringing this issue to our attention and understand your frustration.
Could you please forward us the project link or ID so we can identify the problem?
Looking forward to hearing from you!
Kind regards,
Marina Russo.
https://bunnystudio.com/voice/projects/#/timeline/4574835418E1161DD6FD
VOICE OVER BOOKING PROJECT ID: 4574835418E1161DD6FD
Hi Mark,
Thank you for getting back to me!
I reviewed the project but the instructions appeared as intended for me. See screenshot below:
I believe it must have been a temporary bug, as everything is working as intended now.
If you face this issue again, please message us at support@bunnystudio.com with the project's link and we'll forward it to the engineering team.
Kind regards,
Marina Russo.
Thanks!
BTW, like many things on the platform, it does not appear to be a temporary bug. It has happened before on other projects.
And I'm pretty sure has happened to others.