My support agent didn’t have a memory problem — it was mixing up the same customer 3 different ways

说明与用途

支持代理因 Slack、电子邮件和 HubSpot 的不同标识符而将同一客户误认为三位不同的人。通过实施具有链接身份和事件日志的规范客户实体解决了此问题。

问题

Support agent treated the same customer as three separate entities across Slack, email, and HubSpot, leading to incorrect responses.

结果

Agent no longer confuses the same customer across channels, improving response accuracy and reducing support errors.

工作流

• Identify all channel identifiers for a customer (Slack user ID, email, HubSpot contact ID, Zendesk IDs).
• Create a canonical customer record with an internal ID.
• Store each channel identifier as an alias pointing to the canonical ID.
• Log every interaction as an event tied to the canonical ID.
• When responding, query the canonical record and relevant event slices instead of a full transcript.

证据

The agent had seen: a Slack user ID, an email address, a HubSpot contact

来源

HubSpot strongly pushes email as the primary unique identifier for contacts

来源

Zendesk has the more realistic model for support. A Zendesk user can have multiple identities: email, phone, messaging identity, SDK identity, more. It also supports external_id

来源