Insights
WhatsApp Automation for Zimbabwean Businesses: What to Automate First
The first automation should be a reply your team already sends every day. This note is the order to do that work in. It is not a comparison of WhatsApp products, and it is not a quote.
Start from the messages you already send
Open the chat on the phone that answers customers and scroll back through a normal week. Write down the questions that repeat. The list is often short: are you open, where are you, how much is this, do you deliver to my area, can I send a picture, can I speak to a person. That list is the brief. An automation that cannot answer the top of it, and instead greets people with a menu nobody asked for, has started in the wrong place.
Do this before you choose software. The list also tells you what must stay with a person. If half the chats are “it depends”, because the price depends on a measurement or the stock depends on a delivery, automating a confident answer will create apologies. Collect the repeats first. Then decide which of them are stable enough to hand to a script.
This is not the app-versus-API decision
The WhatsApp Business app, which you install, and the WhatsApp Business API, which software uses, are different products. Which one fits a single phone, a shared inbox, or a reply that has to come from another system is explained in WhatsApp Business app vs API. Read that when you are choosing the tool. This note assumes you are ready to automate something, and it is about the order.
One constraint is worth knowing while you choose what to send. On the API, a message the business starts has to use a template Meta has approved once the customer care window has closed. Meta’s rule is that the window stays open for 24 hours after the customer’s last message. Inside that window you can reply to what they asked. Outside it, you cannot freely message them. That is a reason to automate the reply to an incoming question before you automate a broadcast. People who wrote to you are already waiting. People who did not write are a different, and more restricted, job.
Automate the answers that do not change
First, the facts that are true every day this month. The hours, including Saturday and public holidays you already know you will close. The area you cover, in words a customer uses: Harare only, or Harare and a named list of towns, or “we come to you within this distance”. The address, if customers visit, in the same words as the website and the Google listing. How to start, in one sentence: call this number, send the photo, or ask for a person by name.
Second, the questions that have one answer. “Do you sell this brand?” “Do you deliver to Bulawayo?” “Can I pay by EcoCash?” If the honest answer is “sometimes”, it is not ready to automate. Write the condition in a way a script can say without inventing: “We deliver inside Harare. Outside Harare, a person will confirm.” That sentence is allowed to be boring. Boring and true beats a cheerful guess.
Put these answers where the customer hits them immediately, not behind three menus. Most people write the question in their own words. A system that only understands a button labelled “Option 1” will miss them. Test the real wording, which is the last section of this note.
Then ask three things, and hand the chat to a person
Once the stable answers are in place, the next useful automation is qualification, not a longer speech. Ask for the customer’s name, what they need, and where they are or when they need it. Three questions. Then a person continues, and the person can see what was already said. The customer should be told that a person is picking up. A silent transfer feels like being ignored.
This is the right shape for quotes, bookings that still need a diary, and anything where the answer depends on a look at the job. The automation has saved the person from typing the hours. It has not pretended to be the person. If your team is small, this hand-over is more valuable than a bot that tries to finish the sale. The person was going to finish it anyway. They just start further along.
Leave judgement with a person
Do not automate these, even if they are common:
- Complaints, refunds, and anything that begins with “I am not happy”.
- A price that a person still calculates, including “how much for my house” or “how much for ten, and can you do a discount”.
- Medical, legal or financial advice, where a wrong sentence has a cost the chat cannot see.
- A promise about stock you have not checked today.
- A joke, a flirtation, or an argument. Those need a human, or they need to be ended politely by a human.
Also leave the owner’s family chat alone. If the business number is the same phone that receives personal messages, automation will reply to the wrong people. A business number should be a business number before a script is attached to it. That separation is part of the setup, not a later improvement.
Catalogues, bookings and payments come later
A catalogue is worth connecting when the list is the list you already trust, and someone has the job of updating it. An automated menu of items you sold out of last week creates work, because every chat begins with a correction. The same test applies to a booking step. Connect it to the diary the staff actually use. A second calendar that only the bot can see will double-book the one person who does the work.
A payment step, where the business already has a way to take EcoCash or a card, can sit inside the chat once the earlier answers are reliable. It should not be the first thing you build. If the bot cannot yet say whether you deliver to the customer’s area, taking their money is the wrong milestone. Scope the payment when the conversation up to that point is already right. Provider fees for WhatsApp, and the gateway’s own fees, are not this article’s subject. Confirm those with the provider before you commit. They change, and they are not a design choice.
Use the messages people really send
Customers will not write the sentence you used in the brief. They will write “hi”, then the question, or they will mix English and Shona in one line, or they will send a voice note and a photo of a broken part. If your customers also write in Ndebele, include those messages. An automation that only understands a formal English question will fail in the first afternoon and the team will go back to typing everything.
Collect twenty real incoming messages, with the names removed, and run them through the replies before you let customers meet them. Include the rude ones and the vague ones. For each, decide whether the reply was correct, whether it should have handed over, or whether it invented a fact. Fix those three outcomes. Then watch the first live week and do it again. The person who used to answer the phone is the right reviewer. They know which reply will cause a problem at the counter.
Where a build is discussed
The order above is something you can start on paper this week, even before any software is chosen. When the replies need more than the phone app, the build, including WhatsApp and a chat on the website when the site needs one, is AI automation for Zimbabwean businesses. Bring the list of repeated questions with you. A project that starts from that list is smaller, and more honest, than a project that starts from a demo of everything a bot can say.
The related service
This note explains the topic. The offer sits on AI automation.
Published by Sonke Digital. Questions about a project go through Get a quote, not through this guide.