Messaging and channels

Letting Customers Choose Their Channel: Phone, Chat or Email

How to offer customers a choice of channel without overloading your team: how to find out their preference, record it, respect it and keep replies consistent.

Call editorial team · Published · 5 min read

It sounds obvious that a customer should be allowed to contact you the way they like. In practice many businesses nudge people toward the cheapest channel for themselves, hide the phone number or send everyone to a form. The reasoning is understandable, but a channel the customer dislikes adds effort, and effort is what customers remember.

A customer holding a phone with chat and call icons on the screen
Illustrative image

This guide looks at how to offer a sensible choice, how to learn and store preferences, and how to keep a small team from being swamped. It builds on Omnichannel Support and Customer Experience by Phone.

Why preference matters

People choose a channel for reasons that have little to do with your convenience. A parent at work cannot take a call and prefers a message. An older customer may find typing slow and prefer to talk. Someone reporting a problem with photos wants chat or email. A customer in a hurry wants the quickest route. The right channel for them is the one that costs them the least effort at that moment.

Typical reasons for choosing each channel

  • PhoneUrgent matters, complex or emotional problems, and people who prefer speaking.
  • Chat or messagingQuick questions, sharing images or links, and replying when convenient.
  • EmailDetailed explanations, documents and a written record.
  • Web form or booking pageSimple requests that can be completed without a conversation.

Preferences can also change with the situation. The same person may message to ask about an order and phone to complain about it. A preference is a starting point, not a rule.

Offer only what you can run well

Every channel you open creates a promise. A chat widget that nobody watches or an email address that gets a reply after three days disappoints more than not having one. Start with the channels your customers already use and your team can cover, and add others when you can staff them.

Be honest about channels you do not support. A short note saying that you do not take certain requests by one channel, and why, is better than silence.

Learn and record each customer's preference

The best way to learn a preference is to ask, and the best time is when it is natural: when a customer first signs up, books an appointment or finishes a call. "Is this the best way to reach you, or would you rather we messaged?" takes seconds. You can also observe: which channel they use first and which they reply to.

Putting preferences to work

  1. AskRequest a preferred channel and a good time at sign-up or after a first contact.
  2. RecordStore it on the customer's record, with the date and the source.
  3. UseChoose the channel for call-backs, reminders and follow-ups accordingly.
  4. ReviewCheck at the next contact whether it is still right.

Keep records accurate and limited. Store the preference and consent, not a long profile. Data Minimisation in Support explains why less is better. A customer 360 view puts the preference where every agent can see it.

A customer who prefers messages has not necessarily agreed to marketing messages, and a customer who prefers calls may not want calls at night. Treat preference as how to reach someone for the matter they asked about, and treat consent for marketing separately. Honour opt-outs on every channel, even if the customer only said it on one.

See Opt-Out Management for a way to keep a single list of people who do not want contact, which every channel checks.

Keep the experience consistent

Choice only helps if the answer does not depend on the channel. A customer should not be told one thing by phone and another by email. Use one source of truth for answers, with shared articles and approved replies, and train agents to give the same information however it arrives. Building a Contact Centre Knowledge Base describes how.

Consistent and inconsistent channel service

ConsistentInconsistent
AnswersSame facts on every channel.Different answers depending on who replies.
HistoryEvery agent sees earlier contacts.Each channel is a separate silo.
SwitchingCustomer can move from chat to phone without repeating.Customer starts again each time.
ExpectationsResponse times published for each channel.Customer guesses how long to wait.

Avoid being swamped

A wider choice can raise total contact if the easiest channel becomes the default for everything. Prevent overload by guiding rather than forcing: make self-service answers easy to find, publish response times and move long conversations to the phone when it helps. Watch the mix of contacts across channels and staff accordingly. Response Times for Messages vs Calls describes realistic targets.

Channel choice checklist

  • Channels listed with owners and published hours
  • Response times stated for each channel
  • Preference captured at sign-up and after key contacts
  • Consent and opt-outs recorded separately and checked on every channel
  • Shared answers so replies are the same everywhere
  • A monthly look at contact volume by channel

Accessibility and fairness

Choice is also a matter of access. Some customers cannot use the phone because of a hearing difficulty; others cannot use text or web forms because of a visual impairment, limited literacy or poor connectivity. Offering more than one route means nobody is forced into a channel that excludes them. Make sure the alternative is a real one, with the same quality of service and the same speed, not a slower fallback.

Think about language too. A customer may be happier to write in a second language than to speak it, or the other way around. Let people say which they prefer, and record it. Handling Calls with Vulnerable Customers offers practical advice on adjusting your approach for those who need extra help.

Review how customers actually behave

Once a choice is in place, look at what people do with it. Which channel do first-time customers use? Which do repeat customers use? Where do conversations start and where do they finish? If most chats end in a call, it may be worth surfacing the phone option earlier. If many emails repeat a question that a short answer would settle, put that answer where people will see it. Use the data to refine the offer, not to push everyone toward the channel that is cheapest for you.

Channels in Call

In Call, the Inbox gathers customer messages and phone inquiries in one list that you can filter to a single channel, and a channel that cannot send is marked as not sending. Saved replies are approved per channel, and in the customer's language where one exists. Contacts keep notes, tasks and history, and the unsubscribed list under Message campaigns records people who asked to stop, so campaigns never go to them. Which channels are connected depends on your organisation's setup; WhatsApp voice, for instance, is not offered, though managers can join a waitlist. Text messaging stays off until an operator turns it on.

Frequently asked questions

Should I offer every channel?

No. Offer the ones you can answer promptly and consistently. Add more as your team grows.

How do I find out what a customer prefers?

Ask at a natural moment, such as sign-up or the end of a first contact, and observe which channel they use. Record the answer.

Does a preferred channel mean consent?

No. Preference is about how to reach someone for what they asked; marketing consent is separate and must be recorded.

What if a channel gets too busy?

Publish response times, improve self-service answers and move long conversations to the phone. Staff according to the contact mix.

How do I keep answers consistent across channels?

Use one shared knowledge base and approved replies, and train agents on both.

Can customers change channel mid-conversation?

They should be able to. Make sure the new agent sees the earlier history so the customer does not have to repeat anything.

See every channel in one inbox in Call

In the demo console you can try incoming calls in a simulation.

Related guides