Omnichannel

When a company had one store and one phone line, there was nothing to connect. The customer asked in one place and bought in the same place, and whoever was standing there already knew how far the conversation had gone. That assumption broke as channels multiplied. Ads, a blog, email, app notifications, and a sales line each ended up with a different owner watching a different set of numbers. One person could pass through all five and none of the five would know about the other four.

The problem usually shows up on the customer's side first. Someone clicks an ad, reads the pricing page three times, and submits a sales inquiry. The next morning they get an email that opens with "new here? let us introduce the product." They call, and the rep asks how they first heard about the company. From the customer's side that was one continuous evaluation. From the company's side it was recorded as five separate first meetings that never compared notes.

Omnichannel is the word that turns that disconnect into a named problem. It asks whether the gaps between channels are bridged, not how many channels are running. A company with four channels that share a customer record is doing this; a company with nine channels that don't is not, no matter how the nine are described on a slide.

Pull the scattered records under one person, then let each channel read them before it speaks. Three steps, in order.

1. Resolve the person. The same human is a random browser identifier when they see an ad, an email address when they open a message, and a phone number when they book a call. Without something that declares those three to be one person, none of the later steps hold. The system that ties scattered identifiers to a single customer is called a customer data platform (CDP), and the key it ties them with is usually a login account or an email address.
2. Record what happened at each point of contact. Every place a customer meets the product or the brand is a touchpoint — which ad they clicked, which document they read to the end, where they stopped on the checkout screen — and those events stack up under the same person in time order. Records a company gathers directly on its own channels like this are first-party data.
3. Let the next channel read the record and change what it says. The email going to someone who has viewed pricing three times becomes a customer story rather than a product introduction, and someone who already filed an inquiry stops seeing the same ad. Showing different content to different people is personalization, which is the output of omnichannel rather than its starting point.

Step 1 is where almost everyone gets stuck. The ad tool, the email tool, and the support tool each count people their own way, and companies routinely run for years with three totals that never reconcile. That's why a push toward omnichannel starts in a meeting about where the data will live, not in a meeting about copy.

The term comes up once a company runs more than three or four channels and those channels sit with different owners. Three settings account for most of the usage.

The first is retail with both stores and an app. A cart filled in the app appears on the register screen, something bought in the store lands in the app's purchase history, and a return works anywhere regardless of where the purchase happened.

The second is subscription software. A lapsed free user sees an ad and comes back, reads a blog post, opens a message sent through email marketing, gets a push notification, and eventually talks to sales. Those five steps have to be tied to one record, or the sales rep opens the call as if meeting a stranger.

The third is support. When a conversation moves from chat to a phone call and the customer doesn't have to explain the situation from the beginning again, that is this idea in its narrowest and clearest form.

The reverse case is worth naming too. A company with two channels, both watched by the same person, has nothing to gain from the term. Drawing one customer journey map covers it, and the work of merging data waits until the number of channels that actually need bridging has grown.

"This person filed a sales inquiry yesterday and today we sent them a sign-up nudge."

The channels aren't sharing records, so a customer already in a sales conversation received copy written for strangers.

"Going omnichannel doesn't mean adding channels. It means connecting the four we already run."

Drawing a line between opening a new channel and bridging the existing ones.

"Let's start with not asking people at the sales desk how they found us."

Bridging everything at once is hard, so fix the one gap customers notice most.

At Pagedeck, Ravi runs ads, the blog, and email while Sofia handles sales conversations with incoming accounts. The two worked from different lists, so a few times a quarter Ravi's email kept going to a contact Sofia had already spoken with three times. Adding one rule that removes anyone with a logged sales conversation from the send list cut most of those cases, and the discussion then moved on to where the conversation history should live in the first place.

The most common reading is that running many channels is what makes a company omnichannel. The name invites it — "omni" sounds like a count. But running many channels is just having many channels, while omnichannel describes only the state where those channels are bridged. Treating the two as the same thing means opening one more storefront gets counted as progress. That fifth channel then talks to the same person without knowing what the other four already said, so the customer's impression gets worse while an internal dashboard shows that something was accomplished.

The other common assumption is that buying a tool finishes the job. Products that merge customer data do exist, so the expectation is reasonable enough. What those products actually do is combine records that already share a key. If each channel identifies people by a different value, merging leaves the same human sitting there as three separate customers. Choosing the key and getting every channel to collect it comes first, and that is a decision the channel owners make together about how they record things, not a purchase.