WhatsApp Business API for restaurants and cafés in Kuwait, for the orders you keep

Plenty of Kuwait diners meet a restaurant for the first time on Talabat, Deliveroo, Jahez or Keeta. That order belongs to the app: its customer record, its commission, its promotions. Gallabox has no integration with any of these apps, and orders placed there stay there.

What WhatsApp gives you is a direct line for what the apps handle poorly: the regular who wants 'the usual', the office ordering lunch for the whole team, the family booking a table for Thursday night, the diwaniya that needs trays for the weekend. Those orders carry no app commission, and the customer's number stays with you, with their consent, for next time.

Most restaurants start with a card in the delivery bag or a QR code on the table that says 'Order direct on WhatsApp'. Click-to-WhatsApp ads are the paid version, and every message in a chat that starts from one is free of Meta fees for 72 hours after your first reply.

Direct reorder. Trigger: a customer messages you or taps 'Order' on your Instagram. Message: a list of menu sections, then the WhatsApp catalog. Reply: the customer sends a cart, and the bot asks for pickup or delivery and a location pin. Handover: a person confirms the total and the time, then sends a payment link or marks the order as cash.

Table booking. Trigger: 'Book a table' from the menu. Message: a form for branch, date, time, party size and indoor or outdoor seating. Reply: the request lands in the team inbox, and the host confirms it or offers another slot. A reminder template goes out on the day.

Catering and bulk orders. Trigger: 'Catering' from the menu, or an ad. Message: a form for the event date, number of guests, dishes and delivery address. Handover: always a person, because catering needs a quote. The quote, the deposit link and the final confirmation stay in the same thread.

Feedback. Trigger: an order is marked delivered or a table is closed. Message: one question with three buttons. Reply: good ratings get a thank-you and your review link; poor ones go to the branch manager to call back.

Ramadan changes a restaurant's WhatsApp more than any other month. Opening hours move to the evening, iftar orders bunch up in the hour before maghrib, and ghabga gatherings bring large orders booked days ahead. A chat line that coped in Sha'ban gets swamped.

We set up the Ramadan version before the month starts: a pre-order flow that closes at a cut-off time you pick, a catering form that asks for the ghabga date and headcount up front, and quick replies for the questions that repeat, such as timings, minimum order and delivery areas. Gallabox has no Ramadan-specific feature; this is ordinary flow design, done early.

Changed hours need care. Business-hours rules come with the Essential plan, and holiday schedules for special days such as Eid need Advanced. Basic has no business-hours rules, so hour changes are edited into the bot's messages by hand.

An iftar menu announcement is a marketing message: $0.0341 per delivered message to a Kuwait number until 30 September 2026, and $0.0792 from 1 October 2026, before Gallabox's 15%. Send it to people who opted in and have ordered before, not to every number in the phone.

Order confirmations, booking confirmations and reminders are utility messages; menus, offers and new-branch news are marketing. From 1 October 2026 Kuwait's utility rate is $0.044, and it applies inside the 24-hour chat window too. Replies your staff type are service messages, free up to 1,000 a month per number from October and $0.044 each after that.

A single café or restaurant with two or three people on the chat can run on Basic, at $112 a month billed yearly: catalog, payments, basic forms and five active bot flows. A group with several branches usually needs Essential, at $248 a month billed yearly, for separate teams per branch (up to five), round-robin assignment inside each team, six users, and Conversions API reporting if you run WhatsApp ads.

There is no setup fee on top. Aahfil connects the number, prepares and submits your business verification for Meta to decide on, and writes the first templates for free; the restaurant pays only the Gallabox plan and Meta's fees.

It won't pull orders from the delivery apps or push WhatsApp orders into your POS; Gallabox documents neither. If the kitchen works from the POS, someone keys the WhatsApp order in, or we scope a custom build against the POS's API, if it has one.

In-chat payment isn't available in Kuwait, so KNET and cards go through a payment link from your gateway. And WhatsApp can't speed up the kitchen: if the confirmation promises a time, the kitchen has to meet it, or the channel loses the trust it was built to earn.