Omnichannel Support
"Omnichannel Support is the delivery of customer conversations across phone, web chat, WhatsApp, social, email and SMS with shared knowledge and history."
What is an Omnichannel Support?
Omnichannel Support is the delivery of customer conversations across phone, web chat, WhatsApp, social, email and SMS with shared knowledge and history. Related product: Chat Agents.
Reviewed by Atul Diwedi, Co-Founder · Last reviewed
Deep Dive
Customers do not pick one channel. The same person calls about a quote, follows up on WhatsApp, and sends an email with a photo. Omnichannel support means all of those land with one agent that answers from the same knowledge, recognizes the same customer and keeps the history in one record. The alternative, multichannel, has a presence on every channel but a separate tool, team and memory behind each, which is where the "I already told your colleague" complaint comes from.
How it works. One agent configuration (knowledge base, tools, tone, escalation rules) is published to each channel through that channel's connector: a website widget, the WhatsApp Business API, Instagram and Facebook Messenger, Telegram, Slack, an email address and an SMS number, plus inbound and outbound voice. Each channel has its own format rules: WhatsApp needs approved templates outside the 24-hour window, voice needs short turns and barge-in, email allows long replies and attachments. Identity is matched across channels by phone number and email so the record is shared. Handoff goes to one inbox where a person sees every channel. Reporting is per channel and in total.
Why it matters for support and sales. Coverage on the channels customers already use raises reply rates and lowers the cost of each contact, because a WhatsApp message costs less to handle than a call. Shared knowledge means a price change is updated once. Shared history means the agent on the phone knows what was said in chat yesterday. And a single escalation inbox stops the human team from juggling five tabs.
Example. A dental practice runs the same agent on its phone line, website and WhatsApp. A new patient finds the practice on Instagram and DMs about whitening; the agent answers and asks for a phone number to send the price list. The patient later calls to book; the voice agent matches the number, references the whitening inquiry and books a consultation. A reminder goes by WhatsApp two days before. The patient replies with a question about parking, and the agent answers it in the same thread. The front desk sees one patient record with four touches.
Omnichannel support vs WhatsApp automation. WhatsApp automation is one channel done well: templates, broadcasts, inbound replies and the rules Meta sets. Omnichannel support is the layer that puts WhatsApp next to the phone, the website and email with one agent behind them. Many businesses start with the single channel where their customers are and add the rest.
Common pitfalls. Different knowledge bases per channel that drift apart. Identity not matched, so the same customer is three records. Voice agents given chat-length replies. Ignoring channel rules, such as sending free-form WhatsApp messages after the 24-hour window. Reporting only in total, which hides a channel with a bad resolution rate.
Botcadence runs one platform across 11 channel pages (website chat, WhatsApp, voice inbound and outbound, Telegram, Instagram, Facebook Messenger, Slack, email and SMS) through chat agents and voice agents; see omnichannel support.
Related Technology
See Omnichannel Support in a Botcadence agent
Start on the Free plan and configure an agent that uses Omnichannel Support on your own website chat or WhatsApp number. No card needed.
Get Started FreeWebsite chat live in about 5 minutes
Common Questions
Omnichannel Support FAQs
One or two first, usually the website and the channel most customers already use. Add the rest once the knowledge base is proven, because every channel exposes the same gaps.
By phone number, which both channels provide. Web chat and email need the customer to share a number or email, or to be logged in, before the records can be linked.
No, and it should not have one. One knowledge base feeds every channel; only the reply format changes, such as shorter turns on voice and templates on WhatsApp.
WhatsApp, because Meta verification usually takes 24-48 hours, and managed voice, which takes about 5 business days for number setup and call-flow testing. A website widget can be live in about 5 minutes.