Someone who receives a marketing email might open it tomorrow, or never. Someone who receives a WhatsApp message opens it, usually within minutes. That is the whole advantage, and it is also the whole risk: a channel that lands directly in people's pockets is one you cannot afford to abuse.
What follows is not a list of benefits. It is what to configure, what to connect to your own systems, and where businesses come unstuck — including the things you only find out after you have started.
Two versions, and how to know when to move
The WhatsApp Business app is free and built for a small business: one or two users, a basic catalog, labels for organising customers, quick replies, and automated messages. For most small businesses that is enough, and it is the right place to start.
The WhatsApp Business Platform — what most people call the API — is infrastructure. Several agents on one number, a connection to your CRM, real automation, and everything that requires conversations not to live on somebody's phone.
The signal that it is time to move is almost always the same one: more than one conversation a week falling between the cracks, or a second agent who needs access and cannot have it. Moving earlier is not clever — the API costs money and takes setting up, and a business that does not yet feel the pain is only buying complexity.
The 24-hour window, and templates
This is the part that surprises nearly everyone moving to the API, and it shapes how the whole thing gets built. Once a customer messages you, a 24-hour window opens in which you can reply freely. Outside that window you cannot simply write to them — you have to send a pre-approved template message.
In practice: any enquiry left unanswered for a day stops being a conversation and becomes a pre-approved message that costs money and reads colder. That is the best reason to set a response time and hold to it, and it is an operational reason rather than a service one.
Templates themselves need Meta's approval, and approval takes time. A template written like an advert gets rejected. The ones you will genuinely need — order confirmation, delivery update, appointment reminder — are worth submitting early rather than on the day you need them.
And the pricing has changed more than once in recent years, between per-conversation and per-message billing and by message category. Do not budget from an article, this one included — check Meta's current rates before committing to a volume.
What to set up on day one
A complete profile: name, category, description, address, opening hours, and a link to your site. This is the first impression, and a half-empty profile looks like a personal number pretending to be a business.
A greeting that sets an expectation. Not “Hello, how can we help?” but who you are and how soon you will reply. Someone told they will hear back within two hours waits two hours; someone told nothing goes to a competitor in twenty minutes.
An away message with an actual time in it. “We will reply by 10am tomorrow” beats silence, and it also beats “we will get back to you shortly”, which says nothing.
A priced catalog, if you sell products. It saves an agent typing the same prices for the fifth time that day, and it filters out enquiries outside the budget before they become conversations.
And five quick replies for the five questions that keep coming back. Look at last month's conversations — they are already there.
Three things that turn conversations into sales
Ads that open a conversation directly. Instead of sending someone to a landing page, a form, and a wait for email, the ad starts a chat. For service businesses whose traffic is mostly mobile this often beats a landing page, simply because there is no friction. The trade is that enquiries arrive less qualified, so measure both routes rather than assuming.
Order and delivery updates, and abandoned carts. These are exactly the messages a customer wants, which is what makes them effective: they are service rather than advertising. For a store they also take “where is my parcel” out of the support queue.
Automation, with a layer of judgment on top. Tools like n8n, Make or Zapier can pull the details out of a conversation and put them into a spreadsheet or your CRM without anyone retyping. Above that, a model can classify the enquiry, flag urgency, and draft a first reply — with a person still being the one who sends it.
Consent is not a formality
You cannot send marketing messages to someone who has not explicitly agreed to receive them. That is not a recommendation — it is Meta's own requirement, and it is also the law, whose exact wording depends on where your customer is.
And enforcement here is faster than any regulator: enough people reporting a message as spam is all it takes for the number to be blocked. There is no support queue that gets it back quickly, and that number is the one all of your customers have saved.
So record the consent, record when and where it was given, and give people a simple way out. That is what protects you legally and what keeps the number alive.
Four expensive mistakes
Running the business from a personal number. It looks thrifty on day one, and then come the messages at two in the morning, personal status updates visible to customers, and a number that cannot be handed to anyone else.
Relying on broadcast lists in the app. A broadcast only reaches people who have saved you in their contacts — which is precisely not the new customers you were trying to reach.
Leaving conversations on one device. The day that employee leaves, the history goes with them: who promised what, at what price, and when. A conversation with no central record is a conversation that did not happen.
And not setting response times. Without one there is nothing to measure and nobody to hold to it, and the 24-hour window turns that from a service problem into a recurring cost.
WhatsApp is the lowest-friction channel a business has, which is exactly why it does not tolerate improvisation. What separates a channel that produces sales from a number that gets blocked is configuration, response times, consent kept properly, and a central record.
The technical half — the CRM connection, the automation, the triage — is the part you build once and stop thinking about. That part is ours.