Today's business post is about phone systems for small businesses. Before writing it I read what Google suggests when someone types "business phone system". One of the suggestions was "business phone system with texting".
I recognised it, because a text message is exactly the default I keep having to remove.
The default that kept coming back
In July, a follow-up automation we were building came back with text-message steps already in it. Nobody had asked for them. They were simply the default: a customer does something, and the system sends them an SMS.
It would have worked. It would also have quietly committed the business to a per-message cost that makes no sense for the size of the businesses I work with, on a channel most of their customers do not reply on.
I caught it before it shipped, swapped every text step for a WhatsApp one, and then made it a rule rather than a fix. Every automation we build talks to customers on WhatsApp. If WhatsApp is not connected on an account yet, the build stops and someone gets told. It never falls back to SMS just to keep moving.
Why a default matters more than a decision
Most of the tools I work with were designed somewhere else, for customers who live in their text-message inbox. Here, the conversation is on WhatsApp. That is where people send voice notes, photos of the broken thing, and "are you still coming?" at seven in the morning.
A default is a decision someone else made for a different market. If you do not look at it, you inherit it. Today's search suggestion shows the same assumption in phone systems. The software is fine. The assumption underneath it is not yours.
What it means for calls
This is where the phone comes back in. When a call goes unanswered, the old answer is a text message saying sorry we missed you. What we set up instead is a WhatsApp message to the caller, in the same thread as everything else they have ever sent the business, with someone on the team responsible for the callback.
The point is not WhatsApp for its own sake. The point is that the reply lands where the rest of the conversation already lives, so nobody has to go looking for it on a separate handset.
What I tell owners now
Before you switch on anything that talks to your customers, ask one question: where will their reply go? If the answer is "a phone nobody checks" or "an inbox only one person can see", the default is wrong for you, however good the tool is.
Frequently Asked Questions
Why does NexBDM not use SMS for customer follow-ups?
Because most of our clients' customers reply on WhatsApp, and SMS adds a per-message cost for a channel they rarely answer on. Replies on WhatsApp land in the same thread as the rest of the conversation.
What happens if WhatsApp is not connected yet?
The automation does not go live. It stops and the team is told, so it can be connected properly. We never fall back to text messages just to keep something running.
Does this apply to missed calls too?
Yes. An unanswered call gets a WhatsApp follow-up to the caller, in the same thread as their other messages, with a named person responsible for calling back.