{"id":67,"date":"2026-05-24T02:16:12","date_gmt":"2026-05-24T02:16:12","guid":{"rendered":"https:\/\/jectar.one\/blog\/?p=67"},"modified":"2026-05-24T02:38:51","modified_gmt":"2026-05-24T02:38:51","slug":"whatsapp-chatbot-for-restaurants-build-a-24-7-booking-system-2026","status":"publish","type":"post","link":"https:\/\/jectar.one\/blog\/whatsapp-chatbot-for-restaurants-build-a-24-7-booking-system-2026\/","title":{"rendered":"WhatsApp Chatbot for Restaurants: Build a 24\/7 Booking System (2026)"},"content":{"rendered":"\n

Meta description:<\/strong> Build a WhatsApp chatbot that takes restaurant reservations, answers menu questions, and confirms bookings automatically. Full setup guide for Moroccan restaurants.<\/p>\n\n\n\n

Category:<\/strong> WhatsApp
Read time:<\/strong> 10 min
Target keyword:<\/strong> WhatsApp chatbot restaurant<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Why Your Restaurant Needs a WhatsApp Bot (Not Just WhatsApp)<\/h2>\n\n\n\n

You already have WhatsApp. Every Moroccan restaurant does. The problem isn’t the channel \u2014 it’s what happens on it.<\/p>\n\n\n\n

Right now, your process probably looks like this: customer sends “bonsoir, est-ce que vous avez une table pour 4 ce samedi?” Your manager sees it 45 minutes later between plating orders and managing the floor. Responds. Customer has already booked somewhere else.<\/p>\n\n\n\n

Or worse: Friday night, 8pm, your busiest service. Seventeen unread WhatsApp messages. Your phone is buzzing in your pocket while you’re expediting. You’ll get to them after service \u2014 at 11pm. Half those people wanted tonight. They’re already eating at your competitor’s place.<\/p>\n\n\n\n

A WhatsApp chatbot doesn’t replace the personal touch that makes your restaurant yours. It handles the routine \u2014 the 80% of messages that follow the exact same pattern \u2014 so you handle the 20% that actually need a human.<\/p>\n\n\n\n

\n\n\n\n

What the Bot Handles vs. What Stays Human<\/h2>\n\n\n\n

Bot handles (24\/7, instantly):<\/strong><\/p>\n\n\n\n

    \n
  • “Quels sont vos horaires?” \u2192 automatic response with current hours<\/li>\n\n\n\n
  • “Vous avez de la place ce soir pour 3?” \u2192 checks availability, offers time slots, confirms booking<\/li>\n\n\n\n
  • “C’est quoi votre menu?” \u2192 sends menu catalog or PDF<\/li>\n\n\n\n
  • “O\u00f9 vous \u00eates?” \u2192 sends Google Maps pin + written address<\/li>\n\n\n\n
  • “Vous faites la livraison?” \u2192 sends delivery info or Glovo link<\/li>\n\n\n\n
  • “Vous acceptez les cartes?” \u2192 payment options<\/li>\n\n\n\n
  • Reservation confirmation and reminder messages<\/li>\n\n\n\n
  • Post-visit review request<\/li>\n<\/ul>\n\n\n\n

    Human handles:<\/strong><\/p>\n\n\n\n

      \n
    • “Mon plat \u00e9tait froid et le serveur \u00e9tait d\u00e9sagr\u00e9able” \u2192 complaint needs empathy and resolution<\/li>\n\n\n\n
    • “On veut organiser un anniversaire pour 30 personnes” \u2192 complex event planning<\/li>\n\n\n\n
    • “Est-ce que le chef peut pr\u00e9parer un menu sans gluten pour toute la table?” \u2192 custom request<\/li>\n\n\n\n
    • Any conversation where the customer sounds frustrated or confused<\/li>\n<\/ul>\n\n\n\n

      The rule: if a question has a standard answer, automate it. If it requires judgment, empathy, or creativity, route it to a human.<\/p>\n\n\n\n

      \n\n\n\n

      The Reservation Flow (Step by Step)<\/h2>\n\n\n\n

      Here’s the exact conversation flow your bot should follow. I’m writing it in French because that’s what most Moroccan restaurant bots need, but the same logic works in Arabic or Darija.<\/p>\n\n\n\n

      Customer:<\/strong> “Je voudrais r\u00e9server une table”<\/p>\n\n\n\n

      Bot:<\/strong> “Avec plaisir ! \ud83c\udf7d\ufe0f Pour votre r\u00e9servation, j’ai besoin de quelques infos:<\/p>\n\n\n\n

      Quel jour souhaitez-vous r\u00e9server ?
      1\ufe0f\u20e3 Aujourd’hui
      2\ufe0f\u20e3 Demain
      3\ufe0f\u20e3 Cette semaine (pr\u00e9cisez le jour)
      4\ufe0f\u20e3 Semaine prochaine (pr\u00e9cisez le jour)”<\/p>\n\n\n\n

      Customer:<\/strong> “2” (or “demain”)<\/p>\n\n\n\n

      Bot:<\/strong> “Parfait, demain [Jour, Date]. Pour combien de personnes ?
      1\ufe0f\u20e3 1-2 personnes
      2\ufe0f\u20e3 3-4 personnes
      3\ufe0f\u20e3 5-6 personnes
      4\ufe0f\u20e3 Plus de 6 (un membre de l’\u00e9quipe vous contactera)”<\/p>\n\n\n\n

      Customer:<\/strong> “2” (3-4 personnes)<\/p>\n\n\n\n

      Bot:<\/strong> “3-4 personnes, not\u00e9 ! Quelle heure vous conviendrait ?
      \ud83d\udd50 12h00-13h00 \u2014 Disponible \u2705
      \ud83d\udd50 13h00-14h00 \u2014 Disponible \u2705
      \ud83d\udd50 19h30-20h30 \u2014 2 tables restantes \u26a0\ufe0f
      \ud83d\udd50 20h30-21h30 \u2014 Disponible \u2705
      \ud83d\udd50 21h30-22h30 \u2014 Disponible \u2705”<\/p>\n\n\n\n

      Customer:<\/strong> “20h30”<\/p>\n\n\n\n

      Bot:<\/strong> “Derni\u00e8re \u00e9tape \u2014 \u00e0 quel nom la r\u00e9servation ?”<\/p>\n\n\n\n

      Customer:<\/strong> “Karim”<\/p>\n\n\n\n

      Bot:<\/strong> “Parfait ! Votre r\u00e9servation est confirm\u00e9e \u2705<\/p>\n\n\n\n

      \ud83d\udcc5 Demain, [Date]
      \u23f0 20h30
      \ud83d\udc65 3-4 personnes
      \ud83d\udccd [Nom du restaurant], [Adresse]
      \ud83d\uddfa\ufe0f [Google Maps link]<\/p>\n\n\n\n

      \ud83d\udcdd Nom: Karim<\/p>\n\n\n\n

      Vous recevrez un rappel 2h avant. Pour modifier ou annuler, r\u00e9pondez simplement ici.<\/p>\n\n\n\n

      \u00c0 demain, Karim ! \ud83c\udf7d\ufe0f”<\/p>\n\n\n\n

      Total time: 90 seconds. Zero human involvement. Works at 3am on a Tuesday.<\/p>\n\n\n\n

      \n\n\n\n

      Building This: The Technical Setup<\/h2>\n\n\n\n

      Option A: WhatsApp Business App + Quick Replies (Free, Limited)<\/h3>\n\n\n\n

      If you’re not ready for API access, you can fake a basic version:<\/p>\n\n\n\n

      Create quick replies for the 5 most common questions:<\/p>\n\n\n\n

        \n
      • \/menu<\/code> \u2192 sends your menu<\/li>\n\n\n\n
      • \/horaires<\/code> \u2192 sends your hours<\/li>\n\n\n\n
      • \/adresse<\/code> \u2192 sends location<\/li>\n\n\n\n
      • \/reserver<\/code> \u2192 sends “Pour r\u00e9server, merci d’indiquer: jour, heure, nombre de personnes, et votre pr\u00e9nom”<\/li>\n\n\n\n
      • \/livraison<\/code> \u2192 sends delivery info<\/li>\n<\/ul>\n\n\n\n

        Set away messages for closed hours.<\/p>\n\n\n\n

        This isn’t automation \u2014 it’s organized manual responses. But it’s free and improves response time significantly.<\/p>\n\n\n\n

        Option B: Wati (No-Code, ~$49\/month)<\/h3>\n\n\n\n

        Wati provides a drag-and-drop chatbot builder on top of WhatsApp Business API.<\/p>\n\n\n\n

          \n
        1. Sign up at wati.io, connect your WhatsApp number<\/li>\n\n\n\n
        2. Build the reservation flow visually \u2014 no code<\/li>\n\n\n\n
        3. Create message templates for confirmations and reminders<\/li>\n\n\n\n
        4. Set up team inbox so multiple staff can see conversations<\/li>\n<\/ol>\n\n\n\n

          Pros: Easiest setup. Team inbox. No technical skills needed.
          Cons: Monthly cost. Less flexible than custom n8n solution.<\/p>\n\n\n\n

          Option C: n8n + WhatsApp Business API (Full Control, ~400 MAD\/month)<\/h3>\n\n\n\n

          The setup we recommend for restaurants serious about automation.<\/p>\n\n\n\n

          Infrastructure:<\/strong><\/p>\n\n\n\n

            \n
          • VPS: ~120 MAD\/month (Hostinger, DigitalOcean, Contabo)<\/li>\n\n\n\n
          • 360dialog WhatsApp API: ~300 MAD\/month<\/li>\n\n\n\n
          • n8n: free (open source, self-hosted)<\/li>\n\n\n\n
          • Google Sheets: free (for reservation database)<\/li>\n<\/ul>\n\n\n\n

            The n8n workflow:<\/strong><\/p>\n\n\n\n

            Node 1: WhatsApp Webhook Trigger \u2014 receives incoming messages
            Node 2: Switch node \u2014 checks message content for keywords (“r\u00e9server”, “menu”, “horaires”, “adresse”)
            Node 3 (for reservations): Start reservation flow \u2192 ask date \u2192 wait for response \u2192 ask party size \u2192 wait \u2192 ask time \u2192 wait \u2192 ask name \u2192 wait \u2192 confirm
            Node 4: Add reservation to Google Sheet (Date, Time, Party Size, Name, Phone, Status)
            Node 5: Send confirmation message via WhatsApp
            Node 6: Schedule reminder (2 hours before \u2192 WhatsApp reminder message)<\/p>\n\n\n\n

            Availability checking:<\/strong><\/p>\n\n\n\n

              \n
            • Your Google Sheet has a “Capacity” tab: Date, Time Slot, Total Tables, Booked Tables<\/li>\n\n\n\n
            • Before offering time slots, n8n checks this sheet and only shows slots where Booked < Total<\/li>\n\n\n\n
            • When a reservation is confirmed, n8n increments the Booked count<\/li>\n<\/ul>\n\n\n\n

              For cancellations:<\/strong><\/p>\n\n\n\n

                \n
              • Customer sends “annuler” or “modifier”<\/li>\n\n\n\n
              • Bot asks which reservation (if they have multiple)<\/li>\n\n\n\n
              • Updates the sheet and decrements the capacity count<\/li>\n\n\n\n
              • Sends cancellation confirmation<\/li>\n<\/ul>\n\n\n\n
                \n\n\n\n

                The Menu Bot<\/h2>\n\n\n\n

                Beyond reservations, your bot should handle menu inquiries. Two approaches:<\/p>\n\n\n\n

                Approach 1: WhatsApp Catalog<\/strong>
                WhatsApp Business lets you create a product catalog. Add every menu item with photo, description, and price. When someone asks “c’est quoi votre menu?”, send them the catalog link. They browse it natively inside WhatsApp.<\/p>\n\n\n\n

                Simple. Free. Visual.<\/p>\n\n\n\n

                Approach 2: AI-Powered Menu Q&A<\/strong>
                Connect GPT-4o to your bot. Feed it your complete menu as context. Now customers can ask natural questions:<\/p>\n\n\n\n

                  \n
                • “Qu’est-ce que vous avez pour un v\u00e9g\u00e9tarien?” \u2192 bot recommends vegetarian options from your actual menu<\/li>\n\n\n\n
                • “C’est quoi la diff\u00e9rence entre votre tagine aux pruneaux et le tagine aux olives?” \u2192 bot explains both dishes<\/li>\n\n\n\n
                • “Mon fils a une allergie aux noix \u2014 qu’est-ce qu’il peut manger?” \u2192 bot filters menu items without nuts<\/li>\n<\/ul>\n\n\n\n

                  This feels magical to customers. It costs pennies per conversation in API fees. And it demonstrates a level of service that paper menus never will.<\/p>\n\n\n\n

                  \n\n\n\n

                  The Reminder and Review System<\/h2>\n\n\n\n

                  Once reservations flow through the bot, two follow-up automations become trivial:<\/p>\n\n\n\n

                  Reservation Reminders<\/h3>\n\n\n\n

                  n8n checks the reservations sheet every hour. For any reservation happening in the next 2 hours that hasn’t been reminded yet:<\/p>\n\n\n\n

                  “Bonjour [Pr\u00e9nom] ! Petit rappel : votre table au [Restaurant] est dans 2 heures (\u00e0 [Heure]). \ud83d\udc65 [Nombre] personnes. On vous attend ! \ud83c\udf7d\ufe0f<\/p>\n\n\n\n

                  Si vous avez un emp\u00eachement, r\u00e9pondez ici pour modifier.”<\/p>\n\n\n\n

                  Mark as reminded. If they respond with “annuler” or “reporter”, handle the change flow.<\/p>\n\n\n\n

                  Impact: no-shows drop 40\u201360%. For a restaurant with 30 reservations per evening, preventing even 3 no-shows saves 3 tables’ worth of revenue \u2014 potentially 1,500\u20133,000 MAD per night.<\/p>\n\n\n\n

                  Post-Visit Review Request<\/h3>\n\n\n\n

                  3 hours after the reservation time (enough time for them to finish and leave):<\/p>\n\n\n\n

                  “Merci d’avoir d\u00een\u00e9 chez [Restaurant], [Pr\u00e9nom] ! \ud83d\ude4f Nous esp\u00e9rons que vous avez pass\u00e9 un bon moment.<\/p>\n\n\n\n

                  Si vous avez 30 secondes, un avis sur Google nous aiderait \u00e9norm\u00e9ment : [REVIEW LINK]<\/p>\n\n\n\n

                  \u00c0 bient\u00f4t !”<\/p>\n\n\n\n

                  Send this only once. Don’t nag. The timing (post-meal contentment) and the brevity (30 seconds, one link) maximize the response rate.<\/p>\n\n\n\n

                  \n\n\n\n

                  Handling Edge Cases<\/h2>\n\n\n\n

                  Real conversations aren’t always clean. Your bot needs to handle the messy stuff:<\/p>\n\n\n\n

                  “On sera peut-\u00eatre 4, peut-\u00eatre 6”<\/strong>
                  \u2192 Book for 6 (larger number). Note “flexible party size” in the sheet.<\/p>\n\n\n\n

                  “Est-ce que vous avez une terrasse?”<\/strong>
                  \u2192 Add as a preference field. If you have terrace tables, offer those first. If not, let them know honestly.<\/p>\n\n\n\n

                  “On a un b\u00e9b\u00e9 avec nous”<\/strong>
                  \u2192 Note it. Prepare a high chair if available. The fact that the bot acknowledges this makes the customer feel seen.<\/p>\n\n\n\n

                  “Je veux voir le chef”<\/strong>
                  \u2192 This is a human handoff moment. Bot: “Je transmets votre demande \u00e0 notre \u00e9quipe. Un membre de l’\u00e9quipe va vous r\u00e9pondre dans quelques minutes.”<\/p>\n\n\n\n

                  Messages in Darija<\/strong>
                  \u2192 If using GPT-4o as the brain behind the bot, it handles Darija naturally. “Bghit nrezervi tabla l jouj” \u2192 understood and processed. This is where AI-powered bots genuinely outperform rule-based bots.<\/p>\n\n\n\n

                  Spam or irrelevant messages<\/strong>
                  \u2192 Bot responds once with: “Bonjour ! Je suis l’assistant de [Restaurant]. Je peux vous aider avec : r\u00e9servations, menu, horaires, et adresse. Comment puis-je vous aider ?” If no relevant response, stop responding.<\/p>\n\n\n\n

                  \n\n\n\n

                  Measuring Success<\/h2>\n\n\n\n

                  Track these weekly:<\/p>\n\n\n\n

                    \n
                  • Bot-handled reservations vs. human-handled:<\/strong> Target 70%+ bot-handled within 1 month<\/li>\n\n\n\n
                  • Response time:<\/strong> Should be under 30 seconds for bot responses<\/li>\n\n\n\n
                  • No-show rate:<\/strong> Compare before and after reminder automation<\/li>\n\n\n\n
                  • Review velocity:<\/strong> New Google reviews per week<\/li>\n\n\n\n
                  • Peak hour message handling:<\/strong> How many messages during Friday 7\u20139pm were handled without human intervention<\/li>\n<\/ul>\n\n\n\n
                    \n\n\n\n

                    We build WhatsApp booking systems for Moroccan restaurants. From chatbot to reservation management \u2014 ready in 10 days. Message us: wa.me\/212752138075<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

                    Meta description: Build a WhatsApp chatbot that takes restaurant reservations, answers menu questions, and confirms bookings automatically. Full setup guide for Moroccan restaurants. Category: WhatsAppRead time: 10 minTarget\u2026<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[5,9,4,11],"tags":[],"class_list":["post-67","post","type-post","status-publish","format-standard","hentry","category-ai-automation","category-business-systems","category-tutorials","category-whatsapp"],"acf":[],"_links":{"self":[{"href":"https:\/\/jectar.one\/blog\/wp-json\/wp\/v2\/posts\/67","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jectar.one\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jectar.one\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jectar.one\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jectar.one\/blog\/wp-json\/wp\/v2\/comments?post=67"}],"version-history":[{"count":2,"href":"https:\/\/jectar.one\/blog\/wp-json\/wp\/v2\/posts\/67\/revisions"}],"predecessor-version":[{"id":94,"href":"https:\/\/jectar.one\/blog\/wp-json\/wp\/v2\/posts\/67\/revisions\/94"}],"wp:attachment":[{"href":"https:\/\/jectar.one\/blog\/wp-json\/wp\/v2\/media?parent=67"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jectar.one\/blog\/wp-json\/wp\/v2\/categories?post=67"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jectar.one\/blog\/wp-json\/wp\/v2\/tags?post=67"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}