The arrival of the **[WhatsApp Business API](/fr/blog/whatsapp-business-app-vs-whatsapp-business-api-quand-passer-a-la/)** has caused a rush towards automation in Morocco. E-commerce companies, telecom operators and clinics all want to set up a “Chatbot” (automated conversational agent) to halve the costs of [customer service](/fr/blog/sms-pour-centres-d-call-et-service-client-au-maroc-completer-l/).
However, Moroccan consumers hate feeling like they are “talking to a robot” when they have a real problem. Total, indiscriminate automation often destroys the customer experience and drives down sales. You have to find the balance point. Here's how to design healthy and efficient automation in Morocco.
What a WhatsApp chatbot can (and should) handle alone
The goal of the robot is to absorb the “Low Cognitive Load” (repetitive questions with low added value).
100% automation is recommended for:
- FAQs and Orientation: "What are your hours?", "Where is the Rabat store located?"
- Order Tracking: "Where is my package?" The chatbot, connected to your ERP via a webhook, asks for the phone number, consults the database, and responds instantly.
- Triage (The digital switchboard operator): The bot welcomes the customer with an interactive menu with buttons: "Hello, what are you contacting us about? [1. Purchase] [2. Complaint] [3. Technical support]".
What must absolutely remain human in Morocco
Empathy and flexibility are vital business values in the Moroccan cultural context. Never let a bot manage:
- Negotiation (Haggling): A Moroccan e-commerce customer who asks "Wesh momkin tkhaliha b 200 Dhs?" (Is it possible to make 200 MAD?). If the robot responds with a generic error message, the sale is lost.
- Complex Complaints: "Your delivery person did not call me and canceled the order". An angry customer wants empathy (and an apology), not a multiple-choice menu.
- B2B “High-Ticket” sales: You don’t sell an apartment or a new car via an AI Chatbot. The act of purchasing requires human reassurance.
The Hybrid Model: The bot for sorting, the human for conversion
The best WhatsApp customer service architecture is neither 100% Robot nor 100% Human (too expensive). This is the "Human Handoff".
- The "Menu Bot": The customer initiates the conversation (following receipt of a marketing SMS containing a WhatsApp link). The bot welcomes him and qualifies his request with 2 questions (clickable buttons).
- Data collection: The bot requests the Order Reference and validates the email.
- Handover: As soon as the customer types "Speak to an advisor" or the request is identified as complex, the bot goes "Paused". The conversation appears in the interface (shared Inbox) of the human agent (the sales representative or support), who picks up the thread by reading the qualified history.
Common Conversational Design Mistakes
- The "Cul-de-sac" bot: If the robot does not understand, it loops around saying "I didn't understand". Golden rule: Always leave a way out for the customer (A clear button: “Talk to a human”).
- The fake human: Do not make the customer believe that he is talking to "Sanaa support" if it is a bot. Lying annoys. Say clearly: "Hello, I'm [Brand's] virtual assistant, what can I do for you?".
- Forget the return of Dialectal Arabic (Darija): If you use an advanced generative AI instead of a button menu, be aware that very few AIs perfectly understand Darija written in Latin characters (Franco-Arabic). Prefer WhatsApp's Interactive Buttons: the customer does not have to type text, he clicks, eliminating problems understanding the language.
Frequently asked questions
What is the routing latency on the IAM, Inwi and Orange networks?
On our local routes to Maroc Telecom (IAM), Orange and inwi, the median time to carrier confirmation is 11–17 s (measured in October 2026).
How does the platform manage the format of Moroccan numbers?
EnvoiSMS automatically normalizes the numbers entered (06..., 07..., 00212...) to the E.164 standard (+212) to avoid any delivery failure.