WhatsApp Chatbot Development

AI assistants on the WhatsApp Business API that understand Egyptian Arabic and English, look up real orders and bookings, and pass the hard conversations to your team.

See the work
Platform
WhatsApp Business API on Meta Cloud
Languages
Egyptian Arabic, Franco Arabic and English
Integrations
Shopify, Salla, Zid, WooCommerce and CRMs
You own
Business account, prompts and code
In short

WhatsApp chatbot development covers setting up the WhatsApp Business API on your own Meta account, writing an AI assistant that understands Egyptian Arabic, Franco Arabic and English, connecting it to your store, bookings or CRM for live answers, and handing hard conversations to your team with the full history attached.

  • Business API setup, number verification and message template approval

  • Replies in Egyptian Arabic, Franco Arabic and English

  • Order, booking and CRM lookups from live data

  • Human handoff into a shared inbox with history

  • Guardrails, data limits and conversation logs for review

Overview

WhatsApp chatbot development starts with a simple fact: in Egypt and across the Gulf, customers message a business on WhatsApp long before they fill in a form. A good bot answers those messages properly, in the language people actually type, and knows when to step aside. A bad one sends a numbered menu and loses the customer at the second reply.

01

It fits businesses where the same questions arrive all day. Stores get asked about order status, delivery areas and cash on delivery. Clinics and studios handle bookings and reschedules. Real estate teams qualify interest before a sales call. Service companies triage support requests. If your team pastes the same answer into WhatsApp many times a day, a bot will take that work off them.

It is less useful when every conversation is a negotiation or a custom quote. There the bot's job shrinks to collecting details and routing them to the right person, which is still worth doing.

02

WhatsApp does not allow bots on a personal number. A production bot runs on the WhatsApp Business API, through Meta's Cloud API or a provider, with a verified business, approved message templates for anything sent outside the customer service window, and opt-in rules you have to respect.

On top of that sits the assistant: a model from Anthropic or OpenAI, instructions written for your business, and the tools it is allowed to call. The pieces we usually build:

  • Language handling for Egyptian Arabic, Gulf dialects, Franco Arabic and English, including mixed messages

  • Lookups against your store, booking system or CRM, so answers come from live data

  • Human handoff into a shared inbox with the full conversation attached

  • Template messages for order updates, reminders and follow ups

  • Logs that show what customers ask and where the bot fails

03

Accuracy beats personality. The bot should answer from your real policies and data, say plainly when it does not know, and never invent a delivery date or a price. We set guardrails: topics it will not discuss, actions that need confirmation, and limits on which customer data it can see.

Handoff is the other half. A customer who asks for a person should get one, and the agent who picks up should see the history instead of asking the customer to repeat everything. We judge the bot by resolved conversations and clean handoffs, not by message volume.

04

We start from your real chat history, not a script we imagine. Reading a few weeks of conversations shows which questions repeat, how customers phrase them in Arabic and English, and which ones always end with a human. That becomes the scope for the first version.

We work bilingually, and Arabic first where your customers are, so replies read like someone from your team rather than a translation. The bot connects to what you already run, such as Shopify, Salla, Zid, WooCommerce or your CRM, and to Paymob or Bosta when order questions depend on them. You own the WhatsApp Business account, the prompts and the code. Privacy is planned up front: what gets stored, for how long, and who can read it.

What a WhatsApp assistant needs to work in production, and the order we build it in.

We read a sample of your real WhatsApp conversations with you and sort them: questions the bot can answer alone, questions that need live data, and conversations that should always reach a person. We note how customers write, in Egyptian Arabic, Franco Arabic or English, so the bot is designed around real messages rather than guesses.

  • Egyptian Arabic and English replies

  • Franco Arabic understanding

  • Tone written for your brand

  • Fallbacks when the bot is unsure

  • Meta Cloud API setup

  • Business verification and number onboarding

  • Message template approval

  • Opt-in and service window handling

  • Order status from Shopify, Salla, Zid or WooCommerce

  • Bookings and appointment slots

  • CRM contact and lead updates

  • Delivery tracking with Bosta or Aramex

  • Shared inbox handoff with history

  • Confirmation before sensitive actions

  • Data access limits and retention rules

  • Conversation logs and failure review

There are three common ways to handle customer messages on WhatsApp. They differ in what they understand, what they can look up and how much setup they need.

Business app, menu bot or AI assistant?
WhatsApp Business appMenu bot on the APIAI assistant on the API
Free text understandingNone, your team reads everythingLimited to buttons and keywordsUnderstands natural messages
Egyptian Arabic and FrancoHandled by your teamOnly if keywords are listedHandled, tested on real messages
Live order and booking dataChecked manually by staffPossible through fixed integrationsLooked up through connected tools
Several agents on one numberNot supported on the appSupportedSupported
Setup effortMinimal, install on a phoneModerate, API and flow designHighest, API, instructions and testing
Predictability of repliesDepends on your teamFully predictable, fixed pathsNeeds guardrails and log review

The app suits a small team with light volume. A menu bot fits a few fixed tasks like tracking. An AI assistant fits high volume of varied questions in mixed languages.

It depends on scope more than on the bot itself. The main drivers are how many systems it connects to, how many dialects it must handle, how much handoff logic you need, and running costs: Meta's WhatsApp conversation fees plus model usage. A bot that answers from your policies costs far less than one that reads and changes orders. We price after the chat audit.

Yes. Current Anthropic and OpenAI models handle Egyptian Arabic, Gulf dialects, Franco Arabic and English, including messages that mix them. The work is in the instructions and the testing: we test with real messages from your customers and adjust until replies sound natural and stay accurate. Voice notes need transcription first, so we scope them separately.

For an AI chatbot you need the API. The WhatsApp Business app on a phone offers quick replies and greeting messages, but it cannot run an automated assistant. The API runs on Meta's Cloud API or through a provider, needs a verified business, and lets several agents and the bot share one number. We set it up under your own account.

It hands the conversation to a person. We define the triggers together: the customer asks for a human, the topic is a complaint or refund, the bot is unsure, or an action needs approval. The agent sees the full conversation in a shared inbox and replies from the same number, so the customer never has to start again.

It depends on Meta business verification and template approval, how clean your existing data is, and how many integrations the bot needs. A focused first version that answers common questions and hands off well goes live much sooner than a bot wired into orders, bookings and CRM. We prefer to launch narrow and add capabilities once real conversations show what matters.

You do. The WhatsApp Business account, the number, the prompts, the code and the conversation data stay under your accounts. We agree up front on what the bot stores, how long logs are kept and who can read them, and we send the model only the customer details it needs to answer the question in front of it.

Share a sample of your real chats and we will tell you which questions a bot can answer and which should stay with your team.

Keep exploring
  1. AI & Automation

    (Service)

    Assistants & Chatbots

    Workflow Automation

    Content & Internal Tools

    Engineering & Governance

    Website & WhatsApp assistants

    Customer support bots

    Arabic & English conversation design

    Knowledge-base retrieval (RAG)

    Lead qualification

    AI & Automation — Cairo Studio
  2. Workflow Automation

    (AI & Automation)

    Lead and CRM automation

    Document data extraction

    Syncing and reporting

    Platforms

    Lead capture from forms, ads and WhatsApp

    Routing and assignment rules

    CRM updates and deduplication

    Follow up reminders and tasks

  3. Bilingual Brand Identity

    (Branding & Identity)

    Bilingual typography

    Visual system

    Templates

    Guidelines and handover

    Arabic and Latin typeface pairing

    Type scales for both scripts

    Mixed language line rules

    Font licensing checks

  4. Mobile App Design

    (UI/UX & Product Design)

    Research and scope

    Flows and prototypes

    Interface design

    Systems and handoff

    User interviews

    Reviews of competing apps

    First version feature priorities

    Success criteria for each flow

  5. Next.js & SvelteKit Development

    (Web Development)

    Frameworks

    Headless CMS

    Bilingual and SEO

    Hosting and handover

    Next.js with React and TypeScript

    SvelteKit with TypeScript

    Server rendering and static generation

    API routes and form handling

    Tailwind CSS component systems

  6. Mobile App Development

    (Apps & Platforms)

    App build

    Backend and APIs

    Payments and engagement

    Launch and care

    React Native for iOS and Android

    TypeScript codebase

    Offline states and caching

    Camera, location and media

    Deep links

  7. E-commerce Website Development

    (E-Commerce)

    Platforms and architecture

    Catalog and checkout UX

    Payments and delivery

    Admin and inventory

    WooCommerce development

    Salla and Zid stores

    Headless commerce with Next.js or SvelteKit

    Custom commerce APIs

    Platform migration

  8. Product Photography

    (Content & Production)

    Shot types

    Retouching

    Web delivery

    Campaign assets

    Packshots on white or a solid colour

    Flat lays

    Lifestyle product photos

    Detail and texture close-ups

    Scale and in-hand shots

  9. SEO Services

    (Digital Marketing)

    Technical SEO

    Keyword research

    Content and local

    Reporting

    Core Web Vitals and speed fixes

    Crawl and indexing audits

    Structured data (schema.org)

    Canonicals, redirects and sitemaps

    hreflang and RTL markup