Julien Maneyrol

Thanks for the information Christopher Kennedy,

I guess it is too early to ask, but will there be guides/tutorials to help migrating? I am asking this because we are currently using the Web Widget Classic in some of our products front-ends with advanced customization via its API.

Hi,

I see in the article that the Web Widget (classic) will be phased out in the future. Is there any ETA? How long will it be available?

Hi @...,

I have already sent a ticket and support has recommended posting here. The ticket ID is #11052510.

Dear Zendesk team,

Web Widget(Classic) installed via the installation script  doesn't load in Mozilla Fire Fox (version 108+) when Enhanced Tracking Protection is turned on for the website (Enhanced Tracking Protection is a browser security setting. It can be turned on and off by clicking on the Shield button in front of the address URL > click On button). It seems to only affect macOS and Linux systems; Windows systems are not affected. And it doesn't affect when Web Widget (Classic) is loaded in Zendesk Help Center.

We would like a response from Zendesk product management team on whether or not this can be better controlled from Zendesk's side because this potentially can affect any user who has been using Fire Fox from MacOS or Linux platform after have upgraded the browser to the version of Fire Fox where Enhanced Tracking Protection is turned on (it is turned on by default).

Thank you.
Best regards

Hi John Tieu,

I followed the instructions from this article: https://support.zendesk.com/hc/en-us/articles/4408887368986 to remove placeholders that spammers target in our automatic replies.

Regards

Hi @...,

Thank you very much for the clarification!

I wish it was explicit from the beginning that this feature would be enforced following AB testing, though.

Have a very nice day!

Regards

Hi @...,

I have exactly the same question as Troy: my company has little to no use for this feature and we received the same message. This all seems to imply that the change will be forced on us, while we did not request anything.

Could you provide clarification? Also, will there be a way to keep the old view even after the upgrade?

Thank you.
Best regards

Hi @...,

Thank you for following-up.

The problem has been mitigated by removing placeholders in the automated reply.
Still, being able to fine-tune CPACHA (enforce it under certain circumstances) would be really helpful and much more secure.

Best regards,

Hi @...,

Thanks for your reply.

I understand, but this is not very satisfactory. From my point of view, we - as Zendesk customers - should have the possibility to enforce CAPTCHA to everyone if we need to.

I wish this would be considered as a possible new feature in the future.

Best regards

Hi there,

Is it possible to force offering the CAPTCHA? We have had a massive spam attack from China a couple of weeks ago via one of our contact form from the help center.

The spam attack was obviously done by a bot which used random emails from Chinese hosts IPs.

We have disabled the form and cleaned up our Support (bulk delete spam and users), but we would like to be sure that this won't happen again before re-enabling the form.

Thank you.