BRUTAL MARKETING
OMNICHANNEL CUSTOMER SUPPORT: HOW TO BUILD IT IN A CRM
2026
BRUTAL MARKETING
Omnichannel Customer Support: How to Build It in a CRM
2026
Omnichannel Customer Support: How to Build a Service Where Customers Never Repeat Their Story
A customer messages you on WhatsApp about a late order. The next morning they call, and the agent asks for the order number, asks them to describe the problem again and says, “Let me check, one moment.” An hour later the same customer gets a promo email with a discount on the product they still haven’t received. On paper, your company is present on three channels. In reality, the customer just dealt with three different companies.
Serhii
Ponomarenko
Ponomarenko
This is the norm, not the exception. According to Zendesk CX Trends, 74% of consumers are frustrated when they have to repeat information. In the Genesys State of Customer Experience study, 95% of customers expect a company to remember them regardless of channel. Meanwhile, 48% of organizations don’t even pass data between their chatbot and their human agents. Businesses pay for that gap in churn.
Below is a practical playbook: a maturity test, the four handoffs where context gets lost, the processes to define before you buy software and the metrics that prove the system works. Every section draws on Brutal Marketing client projects.
Below is a practical playbook: a maturity test, the four handoffs where context gets lost, the processes to define before you buy software and the metrics that prove the system works. Every section draws on Brutal Marketing client projects.
What omnichannel customer support is and how it differs from multichannel
Omnichannel support is a model where every channel works as one continuous conversation. A customer starts on Instagram, continues on WhatsApp and finishes with a phone call, and at every step your team sees the full history: what the customer bought, what they asked, what someone promised them and who made that promise.
Multichannel support only looks similar from the outside. The company answers on several channels, but each one lives on its own: its own owner, its own rules, its own “memory.” The result is predictable: customers retell their story every time they switch channels.
Multichannel support only looks similar from the outside. The company answers on several channels, but each one lives on its own: its own owner, its own rules, its own “memory.” The result is predictable: customers retell their story every time they switch channels.
We covered how this difference plays out at the lead generation stage in our piece on how a CRM pulls every channel into one sales system. Here the focus is on support: everything that happens after first contact and after the purchase.
What the gap between channels really costs
Many owners see omnichannel as a nice-to-have for big brands. It’s a revenue question.
A widely cited Aberdeen Group study found that companies with strong omnichannel engagement retain on average 89% of their customers, versus 33% for companies with weak strategies. A study of 46,000 shoppers published in Harvard Business Review showed that customers who use several channels spend 4% more in store and 10% more online than single-channel customers. More recent Genesys research adds that 85% of consumers have spent less or stopped buying from a brand after poor service.
A widely cited Aberdeen Group study found that companies with strong omnichannel engagement retain on average 89% of their customers, versus 33% for companies with weak strategies. A study of 46,000 shoppers published in Harvard Business Review showed that customers who use several channels spend 4% more in store and 10% more online than single-channel customers. More recent Genesys research adds that 85% of consumers have spent less or stopped buying from a brand after poor service.
A sample calculation for a mid-sized business
Take a company that handles 1,500 support requests a month. Thirty percent of them are repeat contacts about the same issue: the customer didn’t get an answer, switched channels or never received the promised callback.
These figures are illustrative, but the math works in any industry. Plug in your own numbers.
- 450 repeat contacts × 7 minutes each = 52.5 agent hours every month.
- At a fully loaded cost of $20 per agent hour, that’s about $1,050 a month, or roughly $12,600 a year.
- If just 5% of those contacts belong to customers who never come back (about 22 people), and each spends $100 per order three times a year, you lose around $6,600 in revenue annually.
These figures are illustrative, but the math works in any industry. Plug in your own numbers.
Quick test: how omnichannel is your support today?
Answer seven questions honestly. Every “no” marks a point where you lose customers.
- Can an agent see a customer’s history from every channel in one view?
- When a customer moves from messaging to a phone call, does the conversation continue instead of starting over?
- Do you have a written first-response target for each channel?
- Do agreements made over the phone get logged in your CRM?
- Does your chatbot pass a conversation summary to the agent when a customer asks for a human?
- Can a sales rep see a customer’s open tickets before calling with a new offer?
- Do you know your top 10 contact reasons from last month as hard numbers rather than gut feeling?
Five levels of omnichannel maturity
In our experience at Brutal Marketing, most small and mid-sized companies that come to us for an audit sit at level 1 or 2. They already bought a CRM or a chat tool but got a single inbox without a single history.
The four handoffs where context gets lost
We keep seeing the same four handoffs where customers have to start their story over.
1. Channel to channel
Problem. A customer messaged you on Viber, didn’t get a reply and called. The agent on the phone can’t see the chat.
Cause. Channels connect to different systems, or to one system that doesn’t merge contacts by phone number, email or messenger ID.
Fix. Deduplicate contacts in your CRM and set a rule: a request continues rather than reopening as a new ticket. On an incoming call, the customer record with recent messages should pop up automatically.
Cause. Channels connect to different systems, or to one system that doesn’t merge contacts by phone number, email or messenger ID.
Fix. Deduplicate contacts in your CRM and set a rule: a request continues rather than reopening as a new ticket. On an incoming call, the customer record with recent messages should pop up automatically.
2. Bot to human
Problem. A customer spent three minutes answering the bot’s questions, tapped “talk to an agent,” and the agent asks the same questions again.
Cause. The bot and the live team work in different tools with no data flowing between them. According to Genesys, that’s how nearly half of companies operate.
Fix. The bot hands the agent a summary: who the customer is, the order number, the issue and what the customer has already tried.
Cause. The bot and the live team work in different tools with no data flowing between them. According to Genesys, that’s how nearly half of companies operate.
Fix. The bot hands the agent a summary: who the customer is, the order number, the issue and what the customer has already tried.
3. First line to specialist
Problem. An agent can’t solve the issue and “passes it to a colleague.” That colleague (an engineer, accountant or warehouse manager) calls the customer and starts from zero.
Cause. Escalation happens in personal messengers or verbally, with no task in the CRM.
Fix. Escalate only through a task on the customer record, with a deadline, a description and an owner. The customer gets a message saying who will contact them and when.
Cause. Escalation happens in personal messengers or verbally, with no task in the CRM.
Fix. Escalate only through a task on the customer record, with a deadline, a description and an owner. The customer gets a message saying who will contact them and when.
4. Support to sales
Problem. A customer has an open complaint, and a sales rep calls to pitch an upgrade. This is the most expensive of the four mistakes, because it destroys trust in a single conversation.
Cause. Sales and support work in different systems or can’t see each other’s statuses.
Fix. An open ticket flags the customer record and pauses automated sales activity, so the rep sees the support status before calling. We explained how to set this up without friction between teams in our guide to CRM for customer service teams and upselling through support.
Cause. Sales and support work in different systems or can’t see each other’s statuses.
Fix. An open ticket flags the customer record and pauses automated sales activity, so the rep sees the support status before calling. We explained how to set this up without friction between teams in our guide to CRM for customer service teams and upselling through support.
Support channels: what each one is for
WhatsApp alone has more than 3 billion monthly users, according to Meta, and messaging is now the default support channel in most markets. The exact mix depends on your region: WhatsApp dominates across much of Europe, Latin America and Asia, Telegram and Viber are strong in Eastern Europe, and SMS still carries a lot of service traffic in the US. Each channel does a specific job.
Messaging apps
For most B2C companies, messaging apps are the main support channel, and customers expect chat speed there. Conversations must live in the CRM, not on the phone of an employee who might leave tomorrow.
On WhatsApp Business Platform, budget for proactive messaging in advance: replies inside the customer service window are free, but template messages your business sends first are mostly paid. On Telegram, Telegram Business lets you connect a chatbot to a business account (with a Premium subscription) to answer routine questions on your behalf.
On WhatsApp Business Platform, budget for proactive messaging in advance: replies inside the customer service window are free, but template messages your business sends first are mostly paid. On Telegram, Telegram Business lets you connect a chatbot to a business account (with a Premium subscription) to answer routine questions on your behalf.
Social media
Instagram DMs often sit with a social media manager who can’t see orders, so the customer gets “we’ll check and get back to you” and then nothing. Connect DMs to your CRM: the social team answers general questions, and anything about an order or a complaint moves to the support queue with the full history.
Phone
Phone is the channel for urgent and emotional situations, and its weak spot is verbal agreements nobody records. At one equipment supplier, we found that about 30% of the promises reps made over the phone never happened. We introduced a rule: after every call, create a CRM task with a deadline. Within a month, the share of fulfilled agreements rose from 70% to 94%.
Email
Email is slow by nature and fits documents, invoices and complex cases. The problem starts when emails live in personal inboxes. Route every customer email to a shared inbox connected to the customer record, so anyone on the team can pick up the thread.
Proactive notifications
The best support request is the one that never happens. Automatic updates about payment, shipping, delays or status changes remove a large share of “where is my order?” questions. In our ecommerce projects, well-configured SMS and messenger notifications cut those requests by 20–30% and support customer retention in ecommerce. We covered ready-made scenarios in our article on automating customer communication in a CRM.
Processes: what to define before you choose any software
The most common mistake is starting with a tool. A CRM only automates the rules you set. If you have no rules, the system faithfully automates chaos.
Before any technical setup, write down answers to five questions:
Define a single tone of voice as well. A customer shouldn’t get a formal “Dear valued customer” by email and “ok, will look” on WhatsApp from the same company. Then train the team on the full customer journey, not only their own channel. We put together detailed customer service quality standards for every communication channel, including phrases to avoid.
Before any technical setup, write down answers to five questions:
- Who owns each channel. A specific name or role, not “the team.” Who covers evenings, weekends and vacations?
- What your response and resolution targets are. Set them per channel; the table above gives starting benchmarks.
- How escalation works. When the system alerts a manager about an unanswered message, which issues go to the second line and in what format.
- What happens when a customer switches channels. The conversation continues on the same record, and the agent doesn’t ask for anything the system already knows.
- How agreements get recorded. Every promise to a customer becomes a task with a deadline and an owner.
Define a single tone of voice as well. A customer shouldn’t get a formal “Dear valued customer” by email and “ok, will look” on WhatsApp from the same company. Then train the team on the full customer journey, not only their own channel. We put together detailed customer service quality standards for every communication channel, including phrases to avoid.
CRM as the core of omnichannel support
Technically, omnichannel support runs on one system that knows everything about the customer, usually a CRM. It covers three core functions.
A unified customer record
The record holds contact details from every channel, purchase history, every conversation, call recordings, open tasks and notes. An agent understands who they’re talking to within 10 seconds. This is also where the system merges duplicates: a customer who messaged on Instagram and called from the same number is one person, not two contacts.
Automatic routing
Requests get assigned by rules: channel, topic, language, customer segment and agent workload. A VIP customer goes to their dedicated manager, a technical question to a specialist, and a new message from a customer with an open complaint to the person already handling it.
SLA monitoring
The system tracks response times and raises the alarm on its own. If a WhatsApp message sits unanswered for 15 minutes, the support lead gets an alert. Without this, the response target in your playbook stays a wish.
Choosing the right setup
Choose based on how many channels you actually use, your monthly request volume and how closely support is tied to sales. If your support team regularly upsells or recovers orders, splitting sales and service into separate systems gets expensive. We described the rollout sequence in our guide to the stages of CRM implementation.
AI agents and chatbots: what to automate and what to keep human
According to Zendesk, 74% of consumers now expect 24/7 service because of AI, and Genesys reports that 76% don’t care whether a person or AI resolves their issue, as long as it’s fast and complete. There’s another side. In a Gartner survey, 87% of customers said companies using GenAI must offer a way to reach a human, and Genesys found that 84% give a virtual agent three attempts or fewer.
The takeaway: an AI agent is a filter and an accelerator, not a wall between the customer and the company.
The takeaway: an AI agent is a filter and an accelerator, not a wall between the customer and the company.
What bots handle well:
- order, shipping and payment status;
- business hours, locations and return policies;
- collecting details before handoff: order number, photos, a short description;
- classifying requests and routing them to the right person;
- answering routine questions from the knowledge base.
What to keep human:
- complaints and conflicts;
- refunds and compensation;
- non-standard requests that need a decision rather than information;
- high-value customers contacting you again about the same issue.
Three rules keep a bot from hurting your service:
- The three-attempt rule. If the bot can’t solve the issue in three steps, it offers an agent on its own.
- A “talk to a human” option is always visible, not buried in the fifth menu.
- The bot passes context. The agent gets a conversation summary and doesn’t ask again.
One more thing: the bot should introduce itself as a bot. In the Salesforce State of the AI Connected Customer report, 72% of customers said it’s important to know whether they’re talking to an AI agent. If you also use chat to sell, see how conversational marketing connects these flows to your pipeline.
Knowledge base: self-service that actually resolves issues
Self-service sounds like the perfect cost saver, but the numbers are sobering. According to Gartner, customers fully resolve only 14% of issues through self-service, and only 36% even among issues they describe as “very simple.” The most common reason for failure: in 43% of cases, customers can’t find relevant content.
Teams often write the knowledge base from memory instead of from real requests. Build yours from CRM data:
That last point is critical: conflicting answers across channels destroy trust faster than having no knowledge base at all. In our experience, a solid knowledge base takes 20–30% of the load off agents within the first few months.
Teams often write the knowledge base from memory instead of from real requests. Build yours from CRM data:
- export contact reasons for the last 2–3 months and take the top 20, which usually cover most of your volume;
- write each article in a “symptom → cause → fix” format;
- add screenshots or a short video for complex actions;
- group FAQs by customer situation (“my order hasn’t arrived,” “I want to return an item”), not by your org chart;
- keep one source of truth: the website, the bot and the agents all use the same content.
That last point is critical: conflicting answers across channels destroy trust faster than having no knowledge base at all. In our experience, a solid knowledge base takes 20–30% of the load off agents within the first few months.
How omnichannel support affects sales
Support isn’t a cost center but part of your repeat sales funnel. Customers whose issues you resolve quickly come back and recommend you more often.
Here’s an example from our practice. A building materials wholesaler received requests by phone, Viber, email and managers’ personal messengers, with no single history and plenty of repeat contacts. We brought the channels into a CRM, set up a unified record, SLAs and escalation, and gave the sales team access to support statuses. Within two months:
That last number matters most to an owner. A support team that sees purchase history can suggest a relevant next step right when the customer is happy with the resolution. We explained how to build this logic in our articles on post-sale strategy for retention and upsells and winning back customers through repeat sales.
One caveat: an upsell is appropriate only after the problem is solved. An offer during an open complaint comes across as disrespect.
Here’s an example from our practice. A building materials wholesaler received requests by phone, Viber, email and managers’ personal messengers, with no single history and plenty of repeat contacts. We brought the channels into a CRM, set up a unified record, SLAs and escalation, and gave the sales team access to support statuses. Within two months:
- CSAT rose from 61% to 79%;
- repeat contacts about the same issue dropped by 38%;
- conversion from a support contact to a repeat order grew from 12% to 19%.
That last number matters most to an owner. A support team that sees purchase history can suggest a relevant next step right when the customer is happy with the resolution. We explained how to build this logic in our articles on post-sale strategy for retention and upsells and winning back customers through repeat sales.
One caveat: an upsell is appropriate only after the problem is solved. An offer during an open complaint comes across as disrespect.
Metrics: how to tell your omnichannel support works
The minimum set is seven metrics, and they belong on one dashboard, not in seven separate reports.
Add one question to your post-contact survey: “Did you have to repeat any information?” It’s the most honest indicator of omnichannel support, because it shows what no technical report can.
Read the metrics together. If FRT drops while repeat contacts grow, agents reply fast but don’t solve problems. If CSAT rises while cost per request spikes, you’re buying satisfaction at too high a price. For ways to raise CSAT systematically, see our guide on improving customer satisfaction with a CRM.
Read the metrics together. If FRT drops while repeat contacts grow, agents reply fast but don’t solve problems. If CSAT rises while cost per request spikes, you’re buying satisfaction at too high a price. For ways to raise CSAT systematically, see our guide on improving customer satisfaction with a CRM.
Five mistakes that keep omnichannel support from working
- Channels connected, data not. Messages land in one interface, but contacts duplicate and history doesn’t link up. Fix: deduplication rules by phone, email and messenger ID from day one.
- Different standards on different channels. WhatsApp gets a reply in 5 minutes, email in two days, Instagram whenever someone remembers. Customers get a lottery instead of service. Fix: one playbook with SLAs for every channel.
- Support and sales live apart. Sales can’t see complaints, and support can’t see deals. Fix: a shared customer record and clear rules for how the teams work together.
- A bot with no way out. The customer loops through menus and leaves for a competitor. Fix: the three-attempt rule and an always-visible “talk to a human” button.
- Omnichannel as a one-off project. Six months after launch you have new channels, new people and the same old problems. Fix: a process owner and a monthly review of metrics and contact reasons. Regular sales and service quality control helps you spot where standards start to slip.
A 90-day rollout plan
For a small or mid-sized business, this takes two to three months, not a year. Here is the sequence we use.
Weeks 1–2. Audit. Map every channel, including the “unofficial” ones: managers’ personal phones, old inboxes, forgotten social pages. Count monthly requests and label each channel as integrated, isolated or losing requests.
Weeks 3–4. Playbook. Assign channel owners and approve SLAs, the escalation path and channel-switching rules.
Weeks 5–8. Technical integration. Connect channels to the CRM and set up the unified record, deduplication, routing and telephony with call recording.
Weeks 9–10. Self-service and bot. Launch a knowledge base covering the top 20 contact reasons and a bot for the 3–5 most common scenarios, with context handoff to agents.
Weeks 11–12. Metrics and first review. Launch the dashboard, collect a month of data and decide what to fix and automate next.
Weeks 1–2. Audit. Map every channel, including the “unofficial” ones: managers’ personal phones, old inboxes, forgotten social pages. Count monthly requests and label each channel as integrated, isolated or losing requests.
Weeks 3–4. Playbook. Assign channel owners and approve SLAs, the escalation path and channel-switching rules.
Weeks 5–8. Technical integration. Connect channels to the CRM and set up the unified record, deduplication, routing and telephony with call recording.
Weeks 9–10. Self-service and bot. Launch a knowledge base covering the top 20 contact reasons and a bot for the 3–5 most common scenarios, with context handoff to agents.
Weeks 11–12. Metrics and first review. Launch the dashboard, collect a month of data and decide what to fix and automate next.
Three steps you can take tomorrow with zero budget
- List every channel customers use to reach you. There are usually two or three more than you thought.
- Set shared response-time targets and tell your team. Even without automation, this changes behavior.
- Log every request in one place, whether that’s a CRM or a shared spreadsheet. In a month, you’ll have real data on contact reasons.
We at Brutal Marketing will select the best CRM program for you to use in your business. We will be happy to tell you about the program's capabilities and show you which settings will exactly help you achieve the desired financial results.
Frequently Asked Questions
What is omnichannel customer support in simple terms?
It’s support where every channel (messaging apps, social media, website chat, phone, email) works as one conversation. The customer can switch channels, and the company still remembers the context.
What’s the difference between omnichannel and multichannel customer service?
Multichannel means being present on several channels that work independently. Omnichannel means connected channels with a shared customer history, consistent standards and end-to-end analytics.
Do we need a separate help desk if we already have a CRM?
Not always. For businesses handling up to a few thousand requests a month, a CRM with connected channels is usually enough. A help desk makes sense with several support tiers and complex routing, but then it needs a CRM integration.
Which support channels matter most?
It depends on your market. For B2C, messaging apps come first (WhatsApp in most regions, Telegram and Viber in Eastern Europe), followed by Instagram, website chat and phone for urgent issues. For B2B, email, phone and messaging. Start where your customers already are.
Can AI agents handle customer support entirely?
No. AI agents handle routine questions, collect details and route requests well, but customers need access to a human, especially for complaints and non-standard cases. The model that works best is a bot as the first line with context handoff to agents.
How do we measure whether omnichannel support works?
Track FRT per channel, FCR, CSAT, repeat contacts and the share of channel switches with preserved history. The survey question “Did you have to repeat any information?” shows the result most accurately.
How long does implementation take?
For a small or mid-sized business, 8–12 weeks from audit to first metrics, of which the technical integration takes 3–4 weeks.
Find out where your customers repeat their story
At Brutal Marketing, we audit support and sales channels: we find where context gets lost, calculate what that costs you and build a plan to bring every channel into your CRM. No templates, just a setup that fits your processes, volume and team.
Book a CRM implementation consultation, and we’ll review your situation and show you where to start this month.
Book a CRM implementation consultation, and we’ll review your situation and show you where to start this month.
By submitting an application, you agree to the privacy policy
© 2017-2027, Brutal Marketing
All rights reserved
© 2017-2027, Brutal Marketing
All rights reserved