Customer context

Merge, export, or erase customer data

Clean up duplicate profiles and handle individual customer data requests.

Owners and administrators can manage duplicate profiles and customer privacy requests from Customers. Choose the correct customer before starting any of these actions.

Merge duplicate profiles

Select the profile you want to merge and choose the destination profile that should remain. Review both identities before confirming.

Conversations, message identity, and widget sessions move to the destination. Non-conflicting custom data is retained; where the same key exists on both profiles, the destination’s value wins.

The source profile is permanently removed. Use a field merge instead if you only want to combine differently named properties, not two people.

Export one customer’s data

Use the customer export action to download a JSON package of their stored support data. It includes profile information, conversations, messages, widget sessions, tags, and attachment metadata.

Private attachment links in the export expire after one hour. Download needed files promptly and store the export securely. If the export reports that it is too large, ask our team for help rather than assuming you received a complete package.

For an integration that reads conversations across inboxes, use the Conversation API instead.

Permanently erase a customer

Use erasure only when you intend to remove that customer’s support data. Type the displayed email address exactly and review the confirmation before proceeding.

Erasure removes the customer and related retained support records; private file cleanup is handled as part of the operation. Check the result for any cleanup error. This is not the same as closing a conversation, and an inbox restore cannot recover independently erased customer data.

Copies already sent to an email recipient or another connected service are not recalled by deleting local support data.

Browse all topics →

Still need a hand? Ask our team.