Agents interacting with authenticated visitors in Zendesk Chat will notice a few key differences.
Authenticated visitors are marked with a green checkmark on their avatar, indicating their verified status. Agents cannot edit the visitor's name or email, as this information is sourced from the authentication data. Additionally, banning an authenticated visitor will prevent them from accessing the Chat widget across all devices and browsers.
To enable authenticated visitors in the Zendesk Chat widget, you need to configure your widget using a new Javascript API and a JWT token. This process involves generating a Chat shared secret and creating a JWT token. The shared secret is a…
Using authenticated visitors in Zendesk Chat provides enhanced security and a seamless experience across devices and domains. With authentication, you can ensure that the visitor is who they claim to be, which increases security and trust. It also…
Generating a shared secret is a crucial step for setting up visitor authentication in Zendesk Chat. To generate a shared secret, navigate to your Chat dashboard, go to Settings > Widget, and click the Widget Security tab. In the Visitor…
Creating a JWT token for Zendesk Chat involves constructing a server-side payload with specific visitor information. The payload should include the customer's name, email, a unique external ID, and timestamps for issued at (iat) and expiration…
Authenticated visitors in Zendesk Chat have a unique widget experience with certain restrictions and benefits. Their information is read-only and cannot be modified through the widget or APIs. Chat sessions are synced across devices, allowing…
Using the $zopim.livechat.clearAll() API in single-page applications has limitations regarding re-authentication. Once this API is called, it logs out the user from the widget, and re-authentication requires a page reload. This is because the…