Question
Some of my visitors change their name during a chat but agents are unable to see this. Why is updated visitor information not reflected in Agent Workspace?
Answer
All changes to visitor information are only applied to a requester in the Agent Workspace if they are made before a visitor initiates a chat or after a chat ends, yet before the next chat session is started. The only exception is the requestor's name which is detailed later in this article.
There are a few different scenarios to take note of if a change is initiated during a chat session:
Updating email to a new address
If a visitor from Chat updates their email to one that does not currently exist in Agent Workspace, a new support user will be created using the new email. The new requester will be applied to the support ticket once a chat ends.
The new user will be created with the name saved with the new email.
To illustrate:
- Visitor A initiates chat with the email address visitora@zendesk.com
- Support ticket created with Visitor A as the requester
- Visitor A edits their name and email to Visitor B, visitorb@zendesk.com(new)
- The agent still sees Visitor A, visitora@zendesk.com as requester
- Agent and visitor ends the chat
- New user Visitor B, visitorb@zendesk.com created
- Ticket updated with new requester Visitor B, visitorb@zendesk.com
Updating email to an existing address
If a visitor from chat updates their email to one that currently exists in Agent Workspace, Zendesk maps the updated email to an existing user. The new requester will then be applied to the support ticket once a chat end event happens.
The name provided from the visitor will be ignored but a notification will appear in the user profile section of Agent Workspace. For the new name to be saved, you can edit the user profile directly in support. Once updated, the notification will disappear.
To illustrate:
- Visitor A initiates chat with email visitora@zendesk.com
- Support ticket created with Visitor A as requester
- Visitor A edits name and email to Visitor C, visitorc@zendesk.com(existing user)
- visitorc@zendesk.com exists in support as Visitor C, visitorc@zendesk.com
- Agent still sees Visitor A, visitora@zendesk.com as requester
- Agent and visitor both end the chat
- Ticket updated with new requester Visitor C, visitorc@zendesk.com
Updating name
If only the name of a visitor is updated, there will be no change to the requester in Agent Workspace and the new name will be ignored. A notification will appear in the user profile section of Agent Workspace. For the new name to be saved, you can edit the user profile directly in Support. Once updated, the notification will disappear.
For more information, see this article: About the Zendesk Agent Workspace
3 comments
Abby
This is incredibly poor behavior. Customers are adding their email address to chat after they've sent their first message, and then we have to re-ask the customer to give us their email if we need it to troubleshoot? Customers are asking why we have to ask them for this again if they've already given it to us. It doesn't make any sense.
0
Miti Shah
Hi Team,
We have gone live with Zendesk in production, but we are encountering a few instances where the external ID and email are not being mapped to the tickets created by chats. We are using Zendesk messaging package 2.14.0v.
Before starting the messaging window, we call the JWT token creation API to authenticate the user with their email ID and our unique external ID. However, in some instances, this information is not getting mapped to the tickets, preventing us from authenticating the user.
Please look into this issue as a priority, as it is affecting our chats.
Instances -
https://nium7225.zendesk.com/agent/tickets/94898/events
https://nium7225.zendesk.com/agent/tickets/93536
https://nium7225.zendesk.com/agent/tickets/93537
0
Miti Shah
++
0