By Andrew Diaz · MAY 09, 2026 · 7 min read
A customer starts in web chat, texts a follow-up an hour later, then calls the next morning. To them it is one conversation. The hard engineering problem is making it one conversation for the system, too.
Routing starts with knowing who you are talking to. We resolve a customer across channels — the same person in a DM and on the phone — so context can follow them. Without that, every channel is an island and the AI re-asks questions the customer already answered.
It is not enough to attach a transcript. The brain carries the state of the conversation: what the customer wants, what has been promised, what is still open. When the channel changes, the goal does not. A booking half-finished in chat is a booking the phone line knows to complete.
Intent decides the path. A product question resolves inline. A scheduling request goes to the calendar. A moment that needs judgment escalates to a person — with the context already gathered. The router’s job is to send each turn to the thing that can actually resolve it.
This only works because there is one approved AI Assistant behind every channel, not four bolted-together bots. Context follows the customer because there is one place for it to live.
The test we hold ourselves to is simple: the customer should never have to repeat themselves because they switched channels.