aiharare· the Harare edition

Insight · Channel

WhatsApp is Harare's CRM: what to build on it, and what not to

In Harare the customer record lives in a chat thread, and POTRAZ's figures explain why. A flow for turning threads into records, and four things not to build.

The numbers behind the habit

Ask a Harare wholesaler where a customer’s order history is and they will scroll. That is not a failure of software adoption; it is a rational response to the market the regulator describes.

  • Mobile is the internet. POTRAZ counted 12.17 million mobile internet subscriptions against 79,416 fibre and 102,105 fixed-LTE subscriptions at Q4 2024. By Q2 2025 there were 11.3 million active mobile data subscriptions averaging ≈3.8 GB a month, against 252,407 fixed subscriptions averaging ≈490 GB. Your customer is on the small number.
  • One app dominates the small number. The last app-level split POTRAZ published (Q2 2018) put WhatsApp at 34.4% of all mobile internet traffic, with WhatsApp and Facebook together at 35.7%. Operators have sold app-specific bundles ever since; nothing since suggests the share fell.
  • One operator dominates the network. Econet held 72.29% of mobile subscribers and 80.89% of data traffic in the quarter to May 2025. When a Harare business says “send it on WhatsApp”, it is usually saying “send it on Econet”.
  • Most businesses are informal. ZimStat’s 2023 Economic Census found 76.9% of establishments informal. An informal business does not buy a CRM licence; it buys a US$1 bundle.
  • Money is in USD and in cash. Over 80% of informal-economy transactions are in US dollars. The thread is where the price was agreed, in which currency, on which date.

So the thread is the record: the enquiry, the quote, the currency, the delivery photo, the complaint. The job is not to replace it. The job is to make it searchable, shareable and safe without asking anyone to change where they type.

The flow: thread to record, and back

WhatsApp thread to business record flow Five boxes left to right: customer message on WhatsApp; structuring step that extracts item, quantity, currency and date; a shared record such as a sheet or diary; a human who owns exceptions; and a confirmation sent back into the same thread. A loop arrow returns from the record to the thread for reminders. Customermessagetext · voice note Structureitem · qty · currency· date · district Recordsheet · diary ·fiscal invoice Personownsexceptions Confirmback inthe thread REMINDERS · PRICE UPDATES · DELIVERY SLOTS RETURN TO THE SAME THREAD Schematic. The thread is never replaced; it is indexed.
Thread → structure → record → person → thread. Original diagram, aiharare.co.zw.

Three design rules make this work in Harare specifically.

Structure, don’t redirect. The failure mode is the link: “please complete your order at our portal”. On a 3.8 GB plan, from a stall in Mbare, that link is a tax. Instead, extract what you need from what they already sent — including transcribing the voice note, which will mix Shona and English and quote a price in USD with change in ZiG — and confirm it back in two lines.

Every record has a currency and a rate date. “US$40 or ZiG at today’s rate” is a Harare sentence. The structured record must carry which currency was agreed and on what date, or the reconciliation at month-end will not close. If you are VAT-registered, the record must also end in a fiscal invoice with the buyer’s TIN, per ZIMRA’s FDMS rules since 31 May 2025.

A person owns exceptions, from a phone. The automation confirms, reminds, restates. It does not negotiate price, promise delivery through a border, or triage a symptom. The hand-off is to a named person, with the thread attached, on their phone — because the office may be dark.

Four things to build first

  1. The order or booking desk. Confirmation with a reference number back in the thread within a minute. This alone removes the “did you get my order?” traffic that eats mornings in Graniteside.
  2. The reminder cadence. Appointment, delivery slot, fee due, script repeat — outbound, scheduled, in the customer’s currency, with a one-word reply to reschedule.
  3. The catalogue with a maintained stock list. WhatsApp Business does this natively; the discipline is the daily update, not the tool.
  4. The proof. Delivery photo, signed quote, fiscal-invoice QR — dropped into the same thread so the record is where the customer will look for it.

Four things not to build

  1. A web portal as the first step. Build it third, if ever, for the office-side users on fibre.
  2. A bot that pretends to be a person. Harare customers know the difference within one message; label it, keep it short, hand off fast.
  3. Anything that stores the thread without a plan. Names, numbers, addresses and health or financial details are personal data under the Cyber and Data Protection Act; POTRAZ is the Data Protection Authority. Decide what you keep, where, for how long, and how someone asks you to delete it — before the first message.
  4. A “smart” price negotiator. Prices in Mbare move by the hour and are set by people. Automate the confirmation of the price, never the price.

Where this applies

The WhatsApp order desk, appointment loop, proof of delivery and parent desk patterns are all instances of the flow above. For the distinction between a workflow like this and an AI agent — and what each costs — the category explainer on aiagent.co.zw is the reference; for implementation, the publisher’s own Zimbabwe site is aiautomatedsolutions.co.zw, disclosed on services in Harare.

Sources

  1. Techzim, Oct 2018 — POTRAZ Q2 2018: WhatsApp 34.4% of mobile internet traffic
  2. Techzim, Sep 2025 — POTRAZ Q2 2025 fixed vs mobile usage
  3. TechNews ZW — POTRAZ Q4 2024 report decoded
  4. Equity Axis, Jul 2025 — Econet market share, quarter to May 2025
  5. ZimStat — Economic Census 2023: 76.9% of establishments informal
  6. Xinhua, 3 Feb 2025 — informal retail and USD share
  7. ZIMRA Public Notice 30 of 2025 — FDMS buyer details
  8. POTRAZ — Data Protection Authority under the Cyber and Data Protection Act

Read next