WhatsApp customer support for Kuwait teams, built to resolve, not just reply

Support on WhatsApp falls apart the moment two people need the same phone. The API fixes that: one business number, many agents, each with their own login, all working from one shared inbox. Chats can be assigned by hand or shared out round-robin within a team, which starts on the Essential plan, and a supervisor can see who is holding what.

The work splits into three layers. A flow-based chatbot takes the questions with one right answer. An AI agent takes the questions people phrase a hundred different ways. Your team takes everything that needs judgement: refunds, complaints, a delivery that went wrong. Each layer has its own page on this site; this one is about how they fit together for a support team.

The handover is where most setups fail. When the bot or the AI agent reaches its limit, the chat should land with the right team, with what the customer already said attached, and the customer should be told that a person is coming. Gallabox has a waiting message for exactly that moment, on every plan.

Until 30 September 2026, every reply your team sends inside the 24-hour customer-service window is free. From 1 October 2026, each business number gets 1,000 free service messages a month, and Meta charges for every one after that. Kuwait becomes its own pricing market on the same day, with a service rate of $0.044 per message before the provider's markup.

For a busy desk that changes what good support looks like. An agent who sends 'hello', 'one moment', 'checking' and 'here you go' as four separate messages spends four service messages on one answer. We write saved replies that finish the job in one message, set the bot to send one complete answer instead of a trickle, and move status questions to a flow that answers once.

It also changes what you measure. Track service messages per solved chat alongside response time, and look hard at conversations that bounce between the bot and a person, because those are the expensive ones. Utility templates sent inside the window, such as an order update, are charged from the same date too, at Kuwait's utility rate of $0.044.

Customers in Kuwait switch between Arabic and English in the same chat, and send a voice note when typing is a nuisance. The practical answer isn't a second number. Ask for the language in the bot's first message, tag the contact with it, and route the chat to agents who are comfortable in that language.

Saved replies and templates need to exist in both languages, written separately rather than translated on the fly. Voice notes still need a person to listen, so they go to the human queue, not the bot. We don't rely on software to understand Kuwaiti dialect; the flows are menu-led, so customers tap instead of type.

Custom inbox views, from Essential, let a supervisor keep the Arabic queue, the English queue and anything waiting too long on one screen.

Most Kuwait support desks work Sunday to Thursday, run lighter cover on Friday and Saturday, and shift to later hours through Ramadan. Business-hours rules, on Essential and above, tell the bot when to promise a quick reply and when to say the team is back in the morning.

Holiday schedules for Eid and national holidays need the Advanced plan. On Essential, we change the hours by hand before each holiday and put the change in the team calendar so nobody forgets. Either way, the after-hours message should say when a person will reply and offer whatever the bot can do in the meantime.

An AI agent is the obvious night shift. It can answer policy and product questions at 1am in Ramadan, and leave anything it can't handle in the morning queue with a note, instead of leaving the customer on read.

Gallabox has no built-in Zendesk or Freshdesk integration. If your tickets live there, we pass chats across through the API or webhooks; full API access starts on Essential. Many smaller desks simply run tickets inside the inbox, with tags, assignment and a resolved status.

Conversation analytics come with every plan and show volume, open and resolved chats and response times. Bot analytics, on Essential and above, show where people leave a flow, which usually means the menu is missing an option. Gallabox lists agent performance analytics as coming soon, so for now we report agent workload from the inbox and its exports.

A satisfaction check can be a one-question flow sent when a chat is resolved. Keep it to one tap, and remember it counts as a service message too.