Key Takeaways
- Business buyers use about 10 channels to engage with companies, and 71% prefer different channels depending on context. There is no single best customer support channel.
- Choose customer support channels by the issues they resolve. Detailed issues go to email or a request form, quick questions to chat, and urgent or sensitive issues to a person.
- Self-service fully resolves only 14% of issues, and chatbots resolve some issue types far better than others. Every channel needs a visible route to a human.
- Each channel you add in a separate tool splits the customer's history. 56% of customers already repeat themselves to different reps.
- The system behind the channels needs one record per account and one knowledge source, not just one inbox.
A new enterprise customer asks for a shared Slack channel. A partner in Brazil asks whether they can message you on WhatsApp. Your help center gets good traffic, but the same questions still arrive by email. And your CEO wants to know why you don't offer phone support like the competitor does.
Each request sounds reasonable on its own. Say yes to all of them, and your team is now watching six places for customer questions, each with its own history. Say no, and customers find you somewhere else anyway. The real decision isn't which channels to add. It's which issues each channel should handle, and what sits behind them all.
What are customer support channels?
Customer support channels are the ways customers reach your team for help. They include email, live chat, phone, video, help centers, AI agents, request forms, messaging apps and shared channels such as Slack Connect. Each channel suits some issues better than others, and most B2B companies run several at once.
Salesforce's survey of 14,300 consumers and business buyers found email is the most-used channel at 93%. Phone followed at 88%, and in person at 86%. Chat was used by 72%, portals by 70%, SMS by 66% and video by 48%. Those are usage rates, not preferences, and the chart combines consumers with business buyers. We found no current public survey that separates B2B channel preference, so treat any list of “customers prefer X” with care.
How to choose customer support channels by issue, not by trend
The evidence points one way: fit depends on the issue, not the channel. Gartner found chatbots resolved 58% of returns and cancellations but only 17% of billing disputes. Self-service fully resolves 14% of all issues, and only 36% of very simple ones. So start with your issue types, not the channel list.
| Issue type | Channels that fit | Why |
|---|
| How-to and known answers | Help center, AI agent, in-app help | The answer exists; the customer wants it now |
| Detailed technical problems | Email, request form, shared channel | Needs logs, screenshots and a written record |
| Quick questions mid-task | Live chat, in-app help | The customer is already in the product |
| Urgent or outage issues | Phone, shared channel, status updates by SMS | Speed and a visible owner matter most |
| Sensitive or high-stakes issues | Phone or video with a person | Customers want a human, not a bot |
| Onboarding and implementation | Video meetings, shared channel, portal | Many people, many weeks, shared tasks |
| Notifications and confirmations | SMS, WhatsApp templates, email | Short, one-way, time-sensitive |
Two rules apply across the whole table. First, every channel needs a route to a person. Gartner found 87% of customers say an option to reach a human is essential when a company uses generative AI. Second, the channel list should follow your customers. A US software company and a company with customers in Latin America will need different messaging apps.
The main customer support channels, one by one
Here is what each channel is good at, where it struggles, and what it needs from the system behind it. Where no outcome data exists, the guidance is reasoned from how the channel works. For the self-service side, see our customer self-service guide.
Email
Best for: Detailed, non-urgent issues that need attachments and a written record. It's still the most-used channel.
Weak for: Urgent issues and outages. In Salesforce's 2022 data, email dropped behind phone as the most-preferred channel.
What it needs: Threading that keeps replies on one case, and a way to see every contact from the same account.
Live chat and in-app help
Best for: Quick questions while the customer is on your site or in your product. In-app help can pass the account, plan and page to the agent.
Weak for: Investigations that run for days. Chat turns async anyway, so the thread has to persist. 76% of customers would choose a company that let them keep text, images and video in one thread.
What it needs: A persistent conversation on the account record, and answers drawn from the same knowledge as the help center.
Phone
Best for: Urgent, sensitive or emotionally charged issues, and customers who want to hear a person.
Weak for: Documentation. What was said lives in someone's memory unless it's written back to the case.
What it needs: A summary on the record after every call, so the next channel starts with context.
Video and screen-share meetings
Best for: Visual troubleshooting, onboarding sessions and escalations with strategic accounts.
Weak for: Volume. It's the least-used channel in Salesforce's data, at 48%, and doesn't scale to routine questions.
What it needs: Meeting notes and next steps saved to the account, not a personal drive.
Help center and customer portal
Best for: Known answers, and letting customers check the status of their own requests.
Weak for: Anything the content doesn't cover. When self-service failed, customers couldn't find relevant content in 43% of cases, and nearly 9 in 10 self-service journeys end up in other channels.
What it needs: Maintained content, and a one-click path from an article to a person that carries the context.
AI agents and chatbots
Best for: Well-defined, repeatable issue types with clear answers.
Weak for: Complex, ambiguous or sensitive issues. Only 27% of customers would retry a chatbot after a bad experience, and 54% of users trust AI with simple issues but not complex ones.
What it needs: The same knowledge your team uses, and a handoff that gives the person the full conversation.
Request forms
Best for: B2B requests that need structured details up front: environment, severity, account and attachments.
Weak for: Anything conversational. Long forms push customers to email instead.
What it needs: Fields that route the request, and a tracked case the customer can follow.
Slack Connect and Microsoft Teams shared channels
Best for: High-touch accounts and implementations where the customer already works in Slack or Teams. A Slack Connect channel can include up to 250 organizations.
Weak for: Tracking. Messages pile up in a busy channel and never become cases. Teams shared channels need cross-tenant setup in each organization.
What it needs: A way to turn a message into a tracked request, and to keep the answer after the channel scrolls. Our Slack Connect support guide covers this in detail.
SMS
Best for: Short status updates, reminders and confirmations. A message holds 160 standard characters, or 70 with an emoji or non-Latin character.
Weak for: Technical issues that need detail or attachments.
What it needs: Consent handling and carrier registration. See our WhatsApp vs SMS guide.
WhatsApp
Best for: Customers and partners in countries where WhatsApp is the default way to message a business.
Weak for: Issues that stay open for days. Outside a 24-hour customer service window, a business can only send approved templates.
What it needs: Approved templates, and a record that survives the window closing.
Social direct messages
Best for: Consumer-facing brands and public complaints.
Weak for: Most B2B support. Messenger gives businesses 24 hours to respond, with a human-agent exception of 7 days.
What it needs: A route from the DM into a tracked case.
Community
Best for: Peer how-to, tips and feature discussion in products with many users.
Weak for: Account-specific or confidential issues.
What it needs: Moderation, and a way to turn good answers into maintained articles.
Why every customer support channel needs one system behind it
Adding a channel is easy. Keeping the customer's story together across channels is hard. Salesforce found 79% of customers expect consistent interactions across departments, yet 56% often have to repeat themselves to different reps. And 55% feel they deal with separate departments rather than one company.
The cause is usually the tools. In HubSpot's survey of 1,537 service leaders, 74% said tool switching slowed ticket resolution. Only 35% of CRM leaders said their customer data was fully integrated with their service tools. Every channel you add in its own tool is another copy of the customer.
B2B makes it worse. An admin emails, an engineer posts in Slack, and a VP raises it on a call. Help desks built for consumers file those as three people with three histories. The record that matters is the account.
And a shared inbox isn't enough. If the help center, the AI agent and your reps each answer from different content, customers get different answers depending on where they ask. The biggest reason self-service fails is content that can't be found. One inbox with three knowledge sources still gives three answers.
What the system behind your customer support channels must do
Put every conversation on the account record
Whichever channel a message arrives in, it should attach to the account. Then anyone serving that customer sees every open thread from every contact.
Answer from one knowledge source in every channel
The help center, the AI agent, chat replies and Slack answers should all come from the same maintained content. Our help center implementation guide covers how to build it. Fix an answer once, and it's fixed everywhere.
Hand off with the full context
When an AI agent or a form hands a customer to a person, that person should see what was already tried. Our guide to human review in AI customer service covers where people belong in the loop. Asking again is the handoff customers notice most.
Measure by account, not by channel
Per-channel metrics can all look healthy while an account is frustrated. Track repeat contacts on the same issue across channels, and whether channels give the same answer.
How to add a new customer support channel without breaking the rest
- Name the issues it should handle. Write down the two or three issue types the channel is for, and which it isn't.
- Connect it to the record before launch. If conversations can't reach the account, don't open the channel yet.
- Point it at the same knowledge. Check that the answers match your help center before customers see them.
- Set a route to a person. Decide who owns the channel, the hours, and how a customer escalates.
- Tell customers what it's for. A support page that says “use chat for quick questions, email for detailed issues” sets expectations.
- Review after 90 days. Check volume, repeat contacts and whether answers stayed consistent. Close channels nobody uses.
MatrixFlows is built on this model. Email, live chat, SMS, WhatsApp, Instagram, Slack and Microsoft Teams conversations land in one inbox. Each attaches to the record your team defines, such as the account. The knowledge base, AI agent and Reply Assistant answer from the same content, and an AI handoff gives the person the full conversation. It has no native phone channel, so phone-heavy teams will pair it with a phone system. See what omnichannel customer service means and our omnichannel software comparison for the wider picture.
Start a free MatrixFlows workspace and connect your channels to one record. Unlimited users, no credit card required.
.svg)
.svg)
.svg)
