Omnichannel
Omnichannel describes support where the customer can write through whichever channel they prefer — chat, email, WhatsApp, phone — and the conversation stays a single thread: the history travels with them and they repeat nothing when switching channel.
What is omnichannel?
Omnichannel describes support where the customer can write through whichever channel they prefer — chat, email, WhatsApp, phone — and the conversation stays a single thread: the history travels with them and they repeat nothing when switching channel.
Also: omni-channel · multichannel
Multichannel is not omnichannel
Multichannel means being on several channels. Omnichannel means they are the same thread. A company with chat, email and WhatsApp handled in three separate inboxes is multichannel, and for the customer that is worse than a single channel: they write on chat, get no reply, write by email, and are picked up by somebody who knows nothing about the first attempt.
Why it matters
What changes in a SaaS
Because the channel switch is where context is lost, and losing context is what raises perceived effort most. For a small SaaS the valuable part is not being in many places: it is that the two or three you are in share the same history.
Omnichannel in detail
What is actually required
A single customer identity across channels and a shared history. Without the first, there is no way to know that whoever writes on WhatsApp is whoever opened the email ticket, and none of the rest matters.
Adding channels has a cost
Every new channel brings its own response-time expectation and its own rules. WhatsApp has a twenty-four-hour window and approved templates; chat expects minutes; email, hours. Opening a channel you cannot sustain is worse than not having it.
The sensible order
Start with the channel people already use, do it well, and add the next when the first stops consuming attention. Most small teams try the opposite.
How Intake handles it
Questions about omnichannel
What is the difference between multichannel and omnichannel?
Multichannel is being present on several channels; omnichannel is the conversation being the same one across all of them, with shared history. Without a single customer identity across channels, what you have is multichannel.
Does a small SaaS need to be omnichannel?
It needs the channels it already uses to share history. Adding channels for the sake of having them multiplies the work without improving the experience.
Related terms
A term on its own is only half understood. These come up in the same conversation.
Shared inbox
A shared inbox is a mailbox the whole team can access, where every conversation has an assigned owner, a status and a history visible to everyone. It replaces forwarding emails between colleagues and the generic address one person quietly runs.
Ticket
A ticket is the record of a customer question inside a support tool. It groups every message in that conversation under one identifier and adds what is needed to manage it: status, owner, priority, tags and the history of what has happened.
Help centre
A help centre is the public site where a company publishes its support documentation so customers can look things up themselves. It combines the articles with a search box, category navigation and, normally, the route to get in touch when the answer is not there.
CES — Customer effort
CES measures how much effort it took the customer to get their problem solved. It is asked with a statement along the lines of "the company made it easy for me" and an agreement scale, and it starts from a specific idea: reducing friction retains people better than trying to delight them.
Help desk — Help desk
A help desk is the team and the tool that receive user questions and resolve them. It centralises in one place whatever arrives by email, chat or form, turns each question into a ticket with a status and an owner, and keeps the history of what was answered.
Support queue
A queue is a set of conversations waiting to be handled by one specific group of people. Splitting the inbox into several queues — by channel, by language, by product or by customer type — is the usual way of dividing the work once a single list stops working.
