WhatsApp automation for a Zimbabwean retailer

Why WhatsApp is the first automation

In Zimbabwe the customer conversation already happens on WhatsApp. POTRAZ’s Q4 2025 sector report puts internet penetration at 84.55%, mobile internet subscriptions at 12.86 million, and WhatsApp at 20.69% of all mobile data — more than double YouTube. Whatever else you automate later, the inbox is where the volume is today, and it is where enquiries are lost.

This guide is written for a shop — hardware, pharmacy, agri-supply, clothing, a small wholesaler — with one to four people answering a business number. It assumes you have nothing but the ordinary WhatsApp app today.

App or Platform: the decision in one table

Start with the app. Most retailers never need the Platform; those who do will know, because the triggers in the last section will be obvious.

Step 1 — Set the free app up properly (one afternoon)

1. Profile. Trading name, physical address as customers describe it (“opposite the Mbare Musika rank”), hours, a real description, website or Facebook page.
2. Greeting message. Sent to new contacts and after 14 days’ silence. Include what you sell, hours, and the one thing people always ask (delivery? EcoCash?).
3. Away message. Scheduled outside hours and used manually during load shedding: “Power is off at the shop until about 14:00. Send your order here; we confirm by 15:00.”
4. Quick replies. Build the ten answers in the WhatsApp reply playbook: prices, hours, location, payment methods, delivery areas and fees, stock check, warranty/returns, opening a business account, “send us a photo of what you need”, “thanks — order received”.
5. Catalogue. Your 40 fastest lines with photo, USD price, and the ZiG price stated with its rate and date. Update the ZiG line when the rate moves; the USD/ZiG sync sheet does the arithmetic.
6. Labels. New enquiry · Quote sent · Order confirmed · Paid · Dispatched · Follow up. Labels are the poor man’s CRM and they work.

Step 2 — One order flow, drawn before it is built

The order sheet is a Google Sheet or Excel Online with one row per order: date, customer name, number, items, USD total, ZiG total and rate, payment method, paid (yes/no), status, dispatched by. For the first month, a person types it. That is the pilot: you are testing whether the flow holds, not whether the software works.

Step 3 — Payment without the back-and-forth

Put the EcoCash merchant code and the USD cash/transfer instructions in one quick reply, and ask for the confirmation screenshot in the same message. POTRAZ counted more than 7 million active mobile money accounts in Q2 2025, with EcoCash holding about 95% of them, so the merchant code is the default. For customers who want to pay by card or ZIPIT, a Zimbabwean gateway such as Paynow supports EcoCash, OneMoney, ZIPIT and cards and can give you a payment link to paste into the chat; fees vary, so ask for the schedule.

Step 4 — Count for a week before you automate anything

Three numbers, written on the wall:

1. Unanswered by close of business. Scroll the inbox at 17:00 and count chats with no reply. This is your lost-revenue line in the ROI calculator.
2. First-reply time. From the customer’s first message to your first human reply, for ten random chats a day.
3. Orders via WhatsApp per day, from the sheet.

A pharmacy that counts 5 unanswered chats a day out of 60 has a bigger problem than typing speed, and a cheaper fix: the away message and quick replies.

When to move to the Platform

The Platform costs money and time to set up (a Meta Business verification, a provider, templates approved by Meta). Move when at least two of these are true:

• More than two people need to answer the same number and the manager cannot see what was promised.
• You need software to send messages: reminders from a booking sheet, “order dispatched” from the order sheet, statements from accounting.
• You are answering more than about 150 conversations a day.
• You run Click-to-WhatsApp ads and want the first three qualifying questions asked automatically.

What the Platform costs for +263 numbers

Meta moved to per-message pricing on 1 July 2025: you pay per template message delivered, in four categories. Service messages — anything you send inside the 24-hour window after a customer messages you — are free. Utility (order confirmations, delivery updates, appointment reminders) is the cheapest paid category and is free when sent inside an open service window. Marketing is the most expensive and has no volume discount. From 1 October 2025 Zimbabwe was moved to Meta’s “Rest of Africa” rate group, so check that row of Meta’s rate card, not “Other”. Your provider (a Business Solution Provider) adds a mark-up — industry guides put it at roughly US$0.003–0.010 per message — or a monthly fee.

Illustrative month for a wholesaler on the Platform: 1,500 customer conversations, all answered inside the 24-hour window (free); 400 “order dispatched” utility templates, of which 250 go out while the customer’s window is still open (free) and 150 are billed; 100 marketing templates to an opt-in list (billed at the marketing rate). The bill is 250 paid messages at a few cents each plus the provider’s fee — tens of dollars, not hundreds. Structure your flows so most messages are replies, and the Platform stays cheap.

Compliance in two lines

Customer numbers and names in a sheet or a CRM are personal data. Under SI 155 of 2024, entities processing personal data for commercial purposes were required to obtain a POTRAZ data-controller licence by 12 March 2025; ask a practitioner whether you are in scope, and never add anyone to a broadcast list who did not ask. WhatsApp restricts numbers that get reported for unsolicited messages, and a banned business number is the most expensive outage there is.

The checklist

• Business profile complete; greeting, away and ten quick replies live.
• Catalogue of the fastest 40 lines, USD and ZiG with rate and date.
• Order sheet with the eleven columns; everyone logs every order for 30 days.
• Three numbers on the wall, counted daily.
• Decision at day 30: stay on the app, or two Platform triggers are true.

Sources