In Kenya, a business number that does not answer WhatsApp is unusual. Customers assume the two are the same thing, message when they feel like it, and are annoyed when nobody replies.
Most businesses arrive at both channels by accident. That is where the trouble starts.
What each is good at
A call wins when the problem is urgent, complicated, or the customer is upset.
Voice carries tone. A difficult conversation that takes four minutes on the phone takes forty messages and ends worse. Anything involving a mistake you have made is a phone call.
A message wins when it is simple, when timing is loose, or when proof matters.
“Is my order ready” does not need a conversation. Neither does sending a reference number, a location, or a photograph of a damaged item. And both sides keep a record, which is genuinely useful when there is a dispute.
The honest summary: calls for conversations, messages for transactions.
The failure that costs the most
Running both channels with no agreement about who watches which.
The pattern is familiar. The phone has a queue, a rota and someone accountable. WhatsApp sits on a handset on a desk, watched by whoever remembers. Messages sit unanswered for hours because everybody assumes somebody else saw them.
Customers do not experience two channels. They experience one business that answered the phone and ignored their message.
If you cannot staff a channel, do not advertise it. An auto-reply saying “we answer messages between 8 and 5, for anything urgent please call” is far better than silence.
Deciding on purpose
Three questions settle it.
Where do your customers already try? Look at where messages actually arrive. If the WhatsApp number is already busy, that decision is made.
What are your calls about? If most are simple status questions, a messaging channel will absorb a lot of them and shorten your queue. If most are complicated or emotional, messaging will not help much and may make things worse.
Who will watch it, on a rota? If the answer is nobody specific, you have your answer.
Running both without dropping either
One record per customer. The single most useful thing. If the person who answers the phone can see that this customer messaged yesterday, they stop asking questions the customer has already answered. Our system puts calls and SMS in one history for exactly this reason.
Agree which channel owns which job. Status questions: messaging. Complaints: phone. Make it explicit so that agents stop guessing.
Move between them deliberately. “This will be quicker if I call you — is now alright?” is a good sentence. So is “I will send you that reference by message so you have it.”
Set hours and say them. Both channels. An auto-reply with real hours is respect; a silent channel is not.
Where SMS still fits
Messaging apps have not removed SMS from this market. SMS still reaches every handset, needs no data, and is read quickly.
It is the right tool for things you send rather than discuss: a payment confirmation, a dispatch notice, an appointment reminder, a one-time code. Our system sends and receives SMS in the same place as calls, so a customer’s texts sit in the same history as their conversations.
That matters more than it sounds. A confirmation message sent at the right moment removes the call that would otherwise follow — which is the cheapest capacity you will ever buy. The arithmetic for that is here.
The short version
- Calls for conversations; messages for transactions
- Do not advertise a channel nobody is rostered to watch
- One customer history across all of them
- Say your hours, on every channel
- Use SMS for the things you send, not the things you discuss