Channel is Not Conversation: The Error of "Omnichannel" Without Continuity

The promise that omnichannel failed to deliver

"Omnichannel" was the retail buzzword of the 2010s. In its original promise, it meant: the customer starts in one channel, continues in another, finishes in a third — and the experience is seamless. The customer experiences the brand, not the channels.

In practice, it became something else: companies present in multiple channels, each operated by a different team, with different systems, without context traveling between them. The customer starts a conversation on WhatsApp, is asked to "open a ticket on the website," repeats everything, is redirected to a phone call, and repeats it all over again. Each channel is a silo. Each handoff is a reset.

Being in more channels without continuity isn't better — it's worse. It multiplies the points where Amnésia Operacional manifests.

The central confusion: channel ≠ conversation

A channel is a physical/logical medium of communication: WhatsApp, email, phone, website chat, form, in-app message. A conversation is the continuous flow of exchange with an identified customer, regardless of the channel used at any given moment.

The rule: a conversation can cross several channels; each channel can carry several conversations.

Teams that confuse the two concepts end up measuring the wrong things:

• "We grew 30% on WhatsApp" — might mean the company fragmented conversations that previously happened through another channel.
• "Our chat response time dropped" — might mean the chat started responding quickly only to then dump the conversation into another channel where the response time increased.

What MCI proposes

In MCI, what is measured and governed is conversation continuity, not channel presence. Key metrics:

• Total conversation time, summing all channels.
• Number of resets (customer re-introducing context, regardless of the channel).
• Identity continuity: percentage of conversations where the same customer individual is recognized across all channels used.
• Context continuity: percentage of conversations where the agent in channel N has access to the context from channel N-1.

Mature MCI operations measure continuity first, channel presence second.

The layer that makes it possible: identity graph + memory

For a conversation to be continuous regardless of the channel, two components are necessary:

1. Identity Resolution (Identity Graph): the same customer individual is recognized as the same identity across all channels — even when identifiers are different (email here, phone there, social ID elsewhere).

2. Layered Memory: what happened in any channel feeds the same operational memory. Context doesn't live in the channel — it lives in the conversation.

Without an identity graph, there is no recognition. Without layered memory, there is no continuity.

When to add a new channel

The practical MCI rule for deciding to enter a new channel:

• Is the customer asking for it? Yes → consider.
• Does the channel integrate into the existing identity and memory layer? Yes → ok.
• Can the team operate through the Bandeja de Contexto, without becoming a silo? Yes → add.

If any answer is no, the channel will become just another silo — and the apparent gain of "we are on channel X" is paid for with a real increase in IAm.

The common case: loose WhatsApp

The most frequent case in Brazilian operations: WhatsApp as the main channel, operated via personal cell phones or an app disconnected from the central system. Each salesperson with their own individual memory. A customer who switches salespeople (vacation, termination) becomes a cold lead.

The fix isn't to "remove WhatsApp" — it's to put WhatsApp into the layer. Official API, conversations indexed by customer identity, messages visible in the Bandeja de Contexto.

The bottom line

Omnichannel without continuity is a translation error: it confused "being in several channels" with "maintaining a continuous conversation." MCI corrects the concept: the work is continuity — channels are a consequence. When you measure it correctly, it becomes clear that adding channels without a layer multiplies problems; and that reducing Amnésia in an existing multi-channel conversation delivers more ROI than opening a seventh channel.