Zendesk shared email: keep each customer’s record separate

Start with the person behind the inbox

When different customers contact you through one inbox, your team still needs to know whose request it is handling. Decide how each person is identified before changing the way your support system stores email addresses.

Zendesk announced shared end-user email addresses on November 3. The option lets separate customer profiles use one email address for contact while retaining their own records and support histories.

It is off by default. It applies to customers using your support service, not staff accounts. The setup guide lists Suite and Support plans, but check your account’s settings before planning a change.

Read the announcement: Zendesk: November 3 shared-email and early-access sign-in announcement.

Choose a customer identifier you can trust

Zendesk normally treats email as a unique identifier. With shared email enabled, the address becomes contact information and a separate External ID links each profile to the customer record in your own system.

That ID could be an existing customer or member number. Have the person responsible for your records decide the mapping and check that two people cannot accidentally be treated as one.

Enabling the feature does not convert existing addresses automatically. Adding an already-used address to another customer can create the shared association. Plan the migration deliberately rather than treating the setting as a complete move.

Check sign-in and message routing

A shared address can receive support notifications and replies. For a customer profile holding it as shared, it cannot serve as the standard email-and-password sign-in or password-reset address. That person needs an address recognised as their own, or an appropriate sign-in connection.

A related option for help-center sign-in without email is in early access. It lets an existing sign-in system identify customers by a unique ID. Enrollment is required, and users without an email still miss features that depend on email delivery.

Also test incoming messages. Zendesk considers address ownership and verification when matching a new email. Replies to existing requests first take account of the people already participating. Do not assume every message from one inbox belongs to the same person.

Make the change reversible in practice

Turning the setting off stops new shared addresses from being created, but existing shared addresses remain. Removing that status requires a separate migration. Ask the administrator to explain the return path before changing live records.

Our perspective: this is useful where a shared contact address reflects the way customers actually work. Keep the current model if it already represents them correctly. No price change is established by the announcement, and sign-in connection work may still need budgeting.

1. Create two approved test profiles with distinct customer IDs and one contact inbox.
2. Test a new email, a reply to an existing request and a support notification.
3. Confirm each customer’s sign-in and recovery method.
4. Approve the migration and return plan before enabling it for real customer records.