In West Africa, WhatsApp is not just another channel: it is the front door of customer service. A shop in Abidjan receives orders, complaints and payment proofs on the same number, often the owner's phone. Messages pile up overnight, customers chase three times, and sales are lost for lack of a reply. An AI agent on WhatsApp does not replace your team: it absorbs repetitive requests and keeps service available around the clock.
Why start with WhatsApp rather than a website
Your customers are already there, with the number you display everywhere. Nothing to install, nothing to explain: they open the conversation they know. A chatbot on your website demands a change of habit and only catches visitors already on the site. WhatsApp catches demand where it is born, receipt photo included. It is also the channel where proof is simplest: the customer shows, the agent verifies, the conversation keeps the record. For an SME, that is the best ratio between launch effort and visible result.
What the agent can actually do
- Track an order and give a reliable delivery date from your logistics API.
- Handle a double charge or an uncredited mobile money payment.
- Verify identity with an SMS code before any sensitive action.
- Answer pricing, opening hours and availability questions from your knowledge base.
- Book an appointment or reservation, then confirm by message.
- Hand off to an advisor with the intent, verified identity and full history.
The difference from a simple auto-reply comes down to one word: action. An agent that promises a refund without checking the invoice creates more problems than it solves. An agent that queries, verifies and acts in your systems saves everyone time.
Three concrete SME scenarios
An online shop receiving 300 messages a week: about 60% ask “where is my order?”. The agent detects the intent, asks for the order number if missing, queries the carrier API and replies with status and expected date. Delivery questions no longer tie up the owner, who focuses on sales and tricky cases.
A medical practice or training centre: requests concern hours, prices, appointment preparation and rescheduling. The agent answers, offers available slots, confirms and sends an SMS reminder. The front desk handles files instead of repeating the same information all day.
A B2B distributor: business customers want an invoice status, a stock level or a restock date. The agent replies in the existing WhatsApp thread, with data from your ERP. The sales rep keeps negotiation and visits, not information digging.
The five building blocks of a reliable agent
- A written procedure: which intent, which verification, which action, which handoff threshold.
- An API for facts: invoice, order, stock, account. Without it, the agent can only chat.
- An OTP code by SMS for sensitive actions: refund, number change, account access.
- A clean human handoff, with context already gathered.
- A conversation log, reviewed during the first week and then by sample.
These blocks are set once in the flow. The agent then applies them to every conversation, at 11:47 PM as at 8:12 AM, with no forgetting and no bad mood.
What it costs, what it returns
Start from your real volume. Take 400 conversations a month, 70% repetitive, at 6 minutes each: that is 28 hours of handling. If the agent resolves 70% without handoff, you recover close to 20 hours a month for your team. Add the sales saved by an answer within seconds and the follow-ups avoided. The agent's cost is usage-based: conversations and AI consumption. So the right question is not “how much does the agent cost”, but “how much does an unanswered conversation cost”.
Deploy in four weeks
- Week 1: write the procedure for a single intent, connect the relevant API, play the scenarios in the simulator.
- Week 2: prepare the WhatsApp Business account and number verification early, then pilot with trusted customers.
- Week 3: add the OTP code and human handoff, review conversations, fix wording.
- Week 4: open more widely, add a second intent, measure the no-handoff resolution rate.
WhatsApp Business verification can take several days: start it in week 1, without waiting for the agent to be perfect.
Expensive mistakes
Promising an instant answer with no API behind it: the agent replies fast but cannot verify anything, and trust drops faster than with an honestly stated delay. Opening to everyone on day one: you drown the flaws instead of fixing them on a small volume. Forgetting the human handoff: the customer loops and gives up. Mixing personal and business numbers: you lose history and credibility. Sending promotions without consent: your number may be blocked and restricted. Finally, not reviewing the first week's conversations: that is exactly where your real intents and your customers' real wording live.
FAQ
Do I need a dedicated WhatsApp Business number? Yes, strongly recommended. It separates private life from customer service, supports several users and keeps a clean history.
What if my customers write in local slang, English or with typos? The agent understands everyday language. Test the local phrasing you actually see in the simulator, then adjust the messages.
What if the customer sends a receipt photo? The agent can request the useful details and hand off the file with the attachment. A refund should never depend on an unverified photo alone.
Does my data stay with me? Your APIs and documents stay yours. The agent accesses them according to declared permissions, and every tool call is logged.
