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

Описание и применение

Агент поддержки ошибочно рассматривал одного клиента как трёх разных из‑за разных идентификаторов в Slack, email и 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

Источник