Since end-users can submit requests using different email addresses and via social media such as Twitter, it's possible that duplicate end-user accounts can be created in your Zendesk.
The user profile allows you to enter multiple email addresses for a user and then set one as primary, which means that regardless of the email address they use to submit a request, they are properly identified and a new user account is not created.
A duplicate user account can also be created if the end-user submits a request via Twitter and their Twitter account has not been added to their user profile.
- Email address
- Twitter account
- Blank/not contact channels
- Direct number
Even though an end-user profile with only a direct number appears in the drop-down menu (shown below), it is not possible to merge into it.
If you try to merge into a profile with only a direct number, you will receive the error message below.
After merging accounts, any tickets created by the duplicate (now merged) account are updated with the primary user account.
- Click the Search icon () in the top toolbar.
- Enter the name of the user you want to merge in the search box and click the user's name when it appears.
Alternatively, you can open a user's profile from one of their tickets.
- Click the User options menu in the upper right, then select Merge into another user.
Zendesk Classic: Select Actions > Merge user.
- Enter the user's name and all users that match what you entered are displayed. Select the correct user and then click Merge.
- When prompted, click Confirm and Merge to confirm the merge. If you want to cancel the merge, close the window instead.
How user data is merged
When you merge one user account into another, the tickets owned by the user account being merged become the tickets of the user that account was merged into and the data in each user profile is combined. The following table describes how user profile data is handled as a result of a merge. The user being merged is referred to as the merging user and the target of the merge is referred to as the receiving user.
|User ticket and profile data||Merge results|
|Tickets||All of the merging user's requested tickets are now requested by the receiving user. CCs are treated similarly.|
|Phone number||Receiving user's value is not affected by merge.|
|Direct Line||Receiving user's value is not affected by merge.|
|Primary email||Receiving user's value is not affected by merge.|
|Secondary email||All secondary email addresses are maintained, merging user's email is added as an additional secondary email address.|
|Language||Receiving user's value is not affected by merge.|
|Time Zone||Receiving user's value is not affected by merge.|
|Organization||Receiving user's value is not affected by merge, but note that tickets aren't automatically updated and may maintain old organization values.|
|Tags||Merging user's tags are lost.|
|Details||Merging user's details are lost.|
|Notes||Merging user's notes are lost.|
|Picture||Receiving user's value is not affected by merge.|
|Custom Fields||Receiving user's custom fields remain intact. Merging user's custom fields are lost.|