Some jurisdictions may require that you provide notice to end users of how their information is shared with third parties, including Zendesk. Although a published privacy policy is helpful, many customers have implemented additional notices and/or consents. Zendesk offers several options to enable you to achieve your compliance goals.
Zendesk offers native functionality to disclose legal terms to your end-users directly within the messaging user experience. You can seamlessly incorporate a link to your privacy notice, which will be seamlessly surfaced to customers at the start of a messaging conversation.
You can also custom-configure web-based conversational widgets – Web Widget, Web Widget (Classic), and Sunshine Conversations Web Messenger – to inform your customers of a privacy notice.
This article discusses the following methods for informing customers of information at the beginning of a chat:
Adding a privacy notice
You can add a privacy notice to a messaging Web Widget. The privacy notice can be included as part of the initial widget configuration process or added to an existing widget.
When added, the text “This chat is recorded using a cloud service.” appears at the top of the messaging widget:
If you’ve published your own privacy documentation, you can also include a link to it as part of the privacy notice. This adds the text “This chat is recorded using a cloud service and is subject to the terms of our Privacy Notice.” to the top of the messaging widget:
To add a privacy notice to a messaging widget
- In Admin Center, click
Channels in the sidebar, then select Messaging and social > Messaging.
- Click the name of the messaging widget you want to update.
- Expand the Basics tab and scroll down to the Privacy notice section.
- Select Add privacy notice.
- Enter a link to your own privacy notice (optional).
- Click Save.
You can remove the privacy notice by deselecting the Add privacy notice setting.
Adding a cookie banner
- “This website uses cookies…”
as well as
- “...we share information about your use of our site with analytics partners according to our Privacy Policy.”
The pop-up can be configured to hide the widget until acknowledged.
If you want the cookie banner to support a “no” option, where the widget will not appear if the customer does not agree to the consent language, you can achieve this via cookie consent technology.
- For Web Widget, see Web Widget API: Set cookies for more information.
- For Web Widget (Classic), see Web Widget (Classic) API: Set cookies for more information.
- For Sunshine Conversations Web Messenger, see Sunshine Conversations Web Messenger API: Set cookies for more information.
Relying on Zendesk branding
By default, the Zendesk widgets include the Zendesk branding. While many customers choose to remove this logo to “white label” the widget if allowed on their account, leaving it in place signals to the end user that the widget experience is powered by a third party.
- For Web Widget, see Configuring the widget frame for more information.
- For Web Widget (Classic), see Configuring components in Web Widget (Classic) for more information.
- For Sunshine Conversations Web Messenger, see Web Messenger: Business profile for more information.
Including a notice in an initial greeting
In Web Widget, you can:
- Update the default message (the first message sent by Web Widget) to describe your privacy policy. This way, if the user does not proceed with a chat, no transcript will be recorded.
- Configure the pre-chat form to send a message to all visitors informing them of your privacy policy.
- Customize the concierge or chat badge to send a message to all visitors informing them of your privacy policy.
- Send an initial greeting in response that describes your privacy policy.
- Include a prechat capture, and configure the greeting to send a message to all visitors informing them of your privacy policy.
- Connect with a cookie bot
Creating a bot with options for refusing consent (Web Widget only)
You can use bot builder to create a conversation bot that informs all visitors of the privacy policy terms. If the user does not consent to this, you should configure bot builder to not transfer their conversation to an agent (after which a transcript is stored).
Admins can put in a message prior to the transfer step to let end users know they will be transferred to an agent and let them know of your privacy policy terms.
0 comments