WhatsApp assistants
WhatsApp AI Assistants That Book, Answer and Escalate — in Arabic and English
In Egypt and the Gulf, WhatsApp is not a support channel — it is the channel. A well-built assistant answers instantly at 11pm, books the appointment, and knows exactly when to stop talking and hand the conversation to a person.
The three jobs a WhatsApp assistant actually does
1. Booking
Reads intent, checks live availability in Google Calendar or your clinic system, offers slots, confirms, writes the booking, and sends a reminder before the appointment. The measurable win is usually no-show rate and after-hours capture.
2. Support triage
Answers the repetitive 80% from your own documents — hours, prices, location, policy, order status — and routes the remaining 20% to the right human with the conversation already summarised.
3. Lead qualification
Asks the three or four questions your sales team asks anyway, scores the lead, writes it to the CRM, and pings the owner on WhatsApp when a serious one appears. Speed-to-first-reply is the single biggest lever on conversion.
A useful assistant does one of these well before it does three badly. We ship the first job, prove it on real traffic, then extend.
Two stacks, compared honestly
Every vendor recommends the stack they resell. Here is the actual trade-off, and we build on both.
| WAHA / self-hosted gateway | WhatsApp Business API via a BSP | |
|---|---|---|
| Setup time | Days. Scan a QR code and you are live. | Weeks. Meta Business verification, display-name review, number migration. |
| Cost model | Server cost only. No per-message fee. | Per-conversation fees to Meta plus BSP margin. |
| Outbound to cold numbers | Fragile and risky — this is not a bulk-messaging tool. | Supported, with pre-approved templates. |
| Compliance / durability | Unofficial. A ban is a real risk if you spam. | Official, contractual, survives scrutiny. |
| Best fit | SMEs, inbound-heavy use, pilots, one number, cost-sensitive. | Regulated industries, multi-agent teams, high outbound volume, brands that need the green tick. |
Our usual recommendation: prove the assistant on a self-hosted gateway where iteration is cheap and fast, then migrate the proven flows to the official API once volume or compliance demands it. We build the logic in n8n either way, so the gateway swap is a change of transport, not a rewrite.
Arabic that actually works
Most "Arabic-supported" bots are an English bot with translated buttons. Real MENA conversations break them within three messages:
- Dialect. Customers write Egyptian, Gulf or Levantine Arabic — not Modern Standard. The assistant has to understand عايز أحجز as readily as أريد الحجز.
- Code-switching and Franco-Arabic. Half-English sentences and Arabic typed in Latin letters with numbers ("3ayez a7gez") are normal, not edge cases.
- Voice notes. A large share of MENA WhatsApp traffic is audio. We transcribe, then treat it as text, then reply in the customer's language.
- Numbers and dates. Arabic-Indic digits, Hijri references, and "بكرة الساعة ٤" all have to resolve to a real calendar slot.
We test against real message logs, not a demo script. If the assistant cannot handle your actual inbox, it is not finished.
Human-in-the-loop by default
This is a design principle we apply to our own internal systems, not a feature we sell. Anything that is irreversible — a price quote, a commitment, an outbound message to a customer who has not written first — passes through a person first.
- The assistant drafts; the operator approves with one tap, inside WhatsApp.
- Confidence and topic thresholds trigger automatic handover instead of a confident wrong answer.
- "Talk to a human" always works, in both languages, at any point.
- Every conversation is logged and reviewable, so you can see what the assistant said and why.
The result is an assistant your team trusts enough to leave on overnight.
Verticals we build for
Clinics and dental practices
Appointment booking against the practice calendar, rescheduling, reminders that cut no-shows, and insurance or pricing FAQs answered in Arabic. Out-of-hours booking capture is usually the whole business case.
Real-estate brokers
Instant reply to portal and Meta Lead Ads enquiries, budget and area qualification, matching listings sent as a carousel, and viewing appointments written to the agent's calendar. In Dubai and Cairo the first responder usually wins the lead.
Restaurants, salons and clinics with walk-ins
Reservations, waitlists, menu and service questions, and confirmation messages — with the assistant standing down automatically during service hours when a human is at the phone.
E-commerce and retail
Order status, returns policy, stock questions, abandoned-cart follow-up on an opted-in list, and escalation to a human for anything involving money.
What it connects to
The assistant is only useful if it can read and write your real systems. Standard integrations: Google Calendar and Google Sheets, Odoo, Zoho CRM and Zoho Bookings, HubSpot, Bitrix24, Shopify and WooCommerce, Airtable, Postgres and MySQL, plus any REST API. Where a system has no API — still common in the region — we integrate through the database or a scheduled export rather than pretending it cannot be done.
Timeline and price band
Pilot assistant (one job, one language, up to three integrations) — USD 500 fixed, live in 10–14 days.
Full bilingual assistant (booking + support + qualification, Arabic and English, CRM and calendar) — from USD 1,200, typically USD 1,200–2,500 depending on integrations.
Managed retainer (monitoring, prompt tuning, new intents, reporting) — from USD 400/month.
Message fees charged by Meta, if you use the official API, are billed by your BSP and are not part of our fee. The pilot price is fixed, not an estimate — if it takes longer than quoted, that is our cost.
Frequently asked questions
Do we need the official WhatsApp Business API?
Not to start. A self-hosted gateway such as WAHA is enough to prove the assistant on inbound traffic, and it is live in days instead of weeks. You need the official API when you send outbound messages at volume, when you have multiple agents on one number, or when your industry requires a contractual provider.
Can the assistant use our existing WhatsApp number?
Yes, though the two paths differ. A self-hosted gateway connects to the number as a linked device. Moving a number onto the official API is a one-way migration and the number leaves the normal WhatsApp app, so we usually pilot on a second number first.
Will it answer in Egyptian or Gulf dialect?
Yes. We tune the assistant to answer in the dialect your customers actually write in, and we test against your real message history rather than a script.
What stops it from saying something wrong to a customer?
Three things: it answers from your documents rather than from open-ended generation, low-confidence or sensitive topics trigger handover to a human, and anything irreversible waits for a one-tap approval from your operator. Every conversation is logged.
How long does it take to go live?
A focused pilot on a self-hosted gateway is 10–14 days at a fixed USD 500. The official API path adds the Meta verification wait, which is outside anyone’s control.
Can it hand over to our human agents?
Yes, and it does so by default. Handover can go to a shared inbox, to a specific person on WhatsApp, or into your CRM as a task, with the conversation summarised so the human does not ask the customer to repeat themselves.
Send us your three most repetitive WhatsApp questions
We will tell you — free — whether an assistant can handle them, which stack fits, and what it would take to go live. If the honest answer is that you do not need one, we will say that too.