WhatsApp chatbots for Kuwait businesses, in Arabic and English

Most WhatsApp traffic to a Kuwait business is the same dozen questions: how much, where are you, are you open, is my order out, can I book Thursday evening. A chatbot answers those in seconds, at any hour, and leaves your team with the conversations that need a human — a complaint, a custom quote, a hesitant buyer.

The good bots are narrow. A clinic bot books, reschedules and sends the location pin. A store bot tells people where their order is and what the return policy says. A real-estate bot asks budget, area and bedrooms before an agent spends a minute. Trying to answer everything is how bots end up answering nothing well.

On the official API the bot runs on your own number, inside your own Meta business portfolio. It is not a script clicking through WhatsApp Web, so there is no risk of the number being shut down for automation that breaks WhatsApp's terms.

Judge a bot by what it takes off the team, not by how many chats it touches. Gallabox's bot analytics show where people leave a flow; the numbers worth watching are how many conversations end without a person, how many people ask for a human at each step, and whether bookings or orders started in the bot actually complete.

A Kuwait bot should ask which language the customer wants in the first message and remember the answer. Everything after that — buttons, confirmations, error messages — needs to exist in both languages, written by someone who speaks both, not run through a translator on the fly.

The Arabic side matters most. Customers here write in Kuwaiti dialect, mix in English words and send voice notes. A menu-led flow handles that well because the customer taps rather than types. Where free text is unavoidable, we write the replies in plain Gulf Arabic and test the flow with real Kuwaiti phrasing before it goes live.

Button labels are short in WhatsApp, so the Arabic has to be written to fit, not squeezed after the fact. That is a copywriting job, and it is most of the difference between a bot people use and one they skip.

Until 30 September 2026, replies inside the 24-hour customer-service window are free. From 1 October 2026 that changes: each business number gets 1,000 free service replies a month, and every reply after that is charged at Meta's service rate. For Kuwait, which becomes its own pricing market on the same day, that rate is $0.044 per message before the provider's markup.

That makes a chatty bot expensive. A flow that sends six short messages where two would do costs three times as much per conversation once you are past the free tier. We design bots to say more per message — a list with every option, one confirmation with the date, time and location together — and to stop talking once the job is done.

Conversations that start from a Click-to-WhatsApp ad are different: Meta keeps every message free for 72 hours after your first reply. A bot that greets ad traffic and qualifies it inside that window costs nothing in Meta fees, which is one reason we build the ads and the bot together.

A flow-based chatbot follows the path you draw. It is predictable, cheap to run and easy to get approved, which is why it should handle bookings, payments links and anything with a right answer.

An AI agent answers in its own words from a knowledge base you give it — your menu, your policies, your price list — and uses AI credits each time it works. It is better at the long tail of questions a menu can't anticipate, and it needs more testing, especially in Arabic. Most businesses we set up start with a flow and add an agent for the questions the flow keeps escalating.

Meta's rules allow AI that helps a business serve its own customers. Since 15 January 2026 they do not allow a general-purpose AI assistant as the product itself. A bot that answers questions about your clinic is fine; a bot that answers questions about anything is not.