# What is Omnichannel?

Also called Omnichannel Support, Unified Channel Experience.

Omnichannel describes an approach where every contact surface, such as chat, email, phone, and messaging apps, feeds one shared record of the customer and their history. A conversation started in one channel can continue in another without the person repeating themselves. It contrasts with multichannel, where the same channels exist but each keeps its own separate history.

The requirement is identity resolution plus a shared conversation store. Contacts arriving on different surfaces have to be linked to the same person, which is harder than it sounds because an email address, a phone number, and an anonymous web session are different identifiers. Once linked, every channel writes to the same timeline and reads the same context.

The visible benefit is not having to repeat an account number three times. The operational benefit is that routing, reporting, and quality measurement work across the whole relationship rather than per channel, so a team can see that a customer tried chat twice before calling. Without that view, each channel reports itself as healthy while the customer's actual experience is poor.

Omnichannel is often claimed for what is really multichannel with a shared inbox. The test is whether context genuinely carries across, including what was promised and what remains open. Channel parity is also frequently misread as a requirement. The goal is continuity, not offering every capability everywhere, since some actions belong on a secure page rather than in a text message.

The hardest part is rarely the technology. It is agreeing which system holds the customer record, what counts as one conversation when it spans four days and three surfaces, and who owns a case that moves between teams. Those decisions determine whether the shared timeline is coherent or merely a merged pile of messages.

## Key points

- One shared history across every contact surface
- Requires linking different identifiers to a single person
- Multichannel offers the same channels with separate histories
- Continuity matters more than identical capability per channel
- Deciding what counts as one conversation is a policy question

## In practice

A customer starts on web chat about a damaged delivery, uploads a photo, and leaves. The next morning she calls. The voice agent recognizes her number, sees yesterday's chat and the photo, and opens with replacement options rather than asking what happened. When she asks for the details in writing, the confirmation email lands in the same case, so all three exchanges sit on one timeline.

## Related terms

- [Channel Routing](/en/glossary/channel-routing)
- [Conversation Thread](/en/glossary/conversation-thread)
- [Chat Widget](/en/glossary/chat-widget)
- [Email Agent](/en/glossary/email-agent)
- [SMS Agent](/en/glossary/sms-agent)

[Back to the AI Glossary](/en/glossary)