Zendesk has introduced a new authentication method for messaging using a signed email and an external ID. This change allows businesses to uniquely identify their end users by combining an external ID with an email address. Developers will need to include a newemail_verified
claim in the JWTs they issue.
This authentication method ensures that agents can verify the identity of end users, access past interactions across various channels, and provide personalized support. It also allows end users to continue conversations and view past interactions across multiple devices, browsers, and channels. For more details, you can check the original announcementhere.
Zendesk introduced signed email authentication to enhance the way businesses authenticate and uniquely identify their end users. By using email addresses, which are widely recognized and used, businesses can provide more personalized support to…
To enable signed email authentication for Zendesk messaging, you need to ensure that messaging is turned on in your account. You will also need to generate a signing key and review the process of using email identities to authenticate end users for…
Developers need to include a newemail_verified
claim in the JWTs they issue as part of the new Zendesk authentication method. This is crucial for ensuring that the end users are authenticated correctly using their email addresses and external…
For more information about Zendesk's authentication updates, you can refer to the guide on enabling authenticated visitors for messaging with Zendesk SDKs. This guide provides detailed instructions on handling verified emails and updates to the…