Zendesk and Sunshine Conversations handle user identities differently. In Sunshine Conversations, a user is identified by an ID, which is the primary identifier in the Sunshine Conversations v2 API. In contrast, Zendesk assigns a userId upon user creation, which appears in the user profile URL and is accessible via the User API.
When a user interacts with messaging, Sunshine Conversations creates a user with an appUserId in the v1 API. If the user is authenticated, an externalId is also associated with them. This externalId helps link the user to the same conversation across multiple devices. In Zendesk, the external_id is used to map incoming conversations with messaging and the Sunshine Conversations externalId. For more details, check out theoriginal link.
End-user authentication plays a crucial role in how user objects are managed in both Zendesk and Sunshine Conversations. When a user is authenticated in Sunshine Conversations, an externalId is associated with their appUserId, allowing the user to…
The externalId serves as a unique identifier for users in both Sunshine Conversations and Zendesk. In Sunshine Conversations, the externalId is set at user creation or through authentication, linking a user to the same conversation across multiple…
When a Sunshine Conversations user sends a new message, Zendesk uses the external_id to map the message to the corresponding Zendesk user. If a ticket already exists and is not closed, new messages are threaded into the existing ticket. If there is…
If a user is unauthenticated in Sunshine Conversations, Zendesk can temporarily track them using their browser session. This allows the system to associate the returning user with the same Sunshine Conversations appUserId, as long as they visit a…