WhatsApp Business API for travel agencies and hotels, ready for Kuwait's peak seasons

Travel enquiries are long and untidy: a family asks about Georgia in July, disappears for a week, then comes back asking about Turkey. The flows below keep that manageable without making the conversation feel like a machine.

Enquiry qualification. Trigger: a traveller messages from an ad, your Instagram bio or the website button. Message: the bot asks where, when, how many adults and children, a rough budget, and which passports they hold. Reply: a few taps, or a typed answer the bot saves as a note. Handover: the chat lands with the agent who handles that destination, brief already written, so the first human reply is a quote rather than a question.

Itinerary and document delivery. Trigger: the booking is confirmed in your system. Message: a utility template with the booking reference, followed by the itinerary, tickets and vouchers as PDFs. Reply: the traveller confirms the names match the passports, or flags a mistake. Handover: a mismatch goes straight to the agent who issued the ticket, because a misspelt name is fixed before departure, not at the airport.

Deposits and balances. Trigger: a quote is accepted, or the balance date is near. Message: a payment link from your gateway, with the amount and what it covers. Reply: the traveller pays on the gateway's page; if the gateway sends a webhook, the chat confirms receipt on its own. Handover: a failed or partial payment goes to accounts.

Before and after the trip. A visa checklist goes out once the destination is fixed, branching on the passports in the family. A reminder with the departure time, meeting point and baggage notes follows a day or two before the flight, and a short feedback question arrives after the return date. Any traveller who answers with a problem reaches a person, not the next automated message.

Meta prices every delivered template by category, and for a travel business the split is clean: anything about a trip the customer has booked is utility, anything that tries to sell a trip is marketing. Until 30 September 2026, Kuwaiti numbers pay Rest of Middle East rates — $0.0341 for marketing, $0.0091 for utility — and replies inside the 24-hour window are free.

From 1 October 2026, Kuwait is priced as its own market: $0.0792 per marketing message and $0.044 per utility message, with utility charged even inside an open 24-hour window. Service replies — ordinary answers in the chat — are free only for the first 1,000 each month per number, then $0.044. Gallabox passes these through with a 15% markup. A traveller roaming abroad on a Kuwaiti number is still billed at Kuwait's rates, because Meta prices by the number's country code.

Two habits keep the bill sensible. Bundle: one confirmation carrying the reference, the dates and the PDF is one message, where four separate notes are four. Answer inside the window: when a traveller has just written to you, a normal reply draws on the free service allowance, while a template sent in the same window is charged.

Peak-season offers are where costs climb. An Eid or summer package blast is marketing at $0.0792 a message, WhatsApp caps how many marketing messages each person receives, and blocked sends come back with error 131049. Segment by past trips and send smaller, relevant batches instead of the whole list. Travellers who arrive from a Click-to-WhatsApp ad are different: once you reply within 24 hours, every message for 72 hours is free — useful for a trip that takes a few days to decide.

Demand here arrives in waves: the summer break when schools close, both Eid holidays, and the national holidays in February. Enquiries pile up within a few weeks, and a team answering each one by hand either slows down or stops qualifying. The bot handles the first round of questions so agents spend the peak on quotes.

Bookings are often for a whole family, which means several passports, children's ages that change the fare, and one person paying for everyone. The flow collects each traveller's details as a list, and the documents come back into the same chat, tagged to the booking.

Umrah packages have their own rhythm: group departures, a fixed document list, and a coordinator travellers need to reach. WhatsApp handles the logistics well — flight times, hotel details, the coordinator's number, what to pack — and nothing beyond that. Religious guidance stays with the people qualified to give it, not with a bot.

Visa requirements depend on the passport, and a Kuwait agency serves citizens and residents holding many different ones. The checklist branches on nationality and comes from your team's own current list for each destination: the bot sends what you wrote and never guesses what an embassy asks for.

Arabic and English both matter. Families often plan in Arabic while tickets and vouchers come in English. Templates are approved in both languages, and the traveller picks one at the start.

Basic ($112 a month billed yearly) suits a small agency: 3 users at most, 5 active bot flows, 10K broadcast contacts a month, and basic forms for enquiries. It has no drip campaigns, which is the catch for travel, where much of the value sits in timed reminders.

Essential ($248 a month billed yearly) is where most agencies land. It adds drip campaigns (up to 10 sequences) for pre-departure timelines, 6 users, 20 active flows, AI agents on WhatsApp that answer package questions from your own documents, and bot business hours.

Advanced ($474 a month billed yearly) earns its price for two travel reasons: holiday schedules, so the bot knows the office is closed over Eid, and dynamic forms, which let a visa checklist change as the traveller answers. Hotels with separate reservations and front-office teams also use its 10 users and custom roles. Setup through Aahfil is free — connecting the number, preparing business verification (Meta decides the outcome) and the first templates — so what you pay is the plan and Meta's message fees.

Gallabox doesn't connect to airline or booking systems out of the box. Flight changes and live availability reach WhatsApp only if your booking platform calls the Gallabox API or sends a webhook; otherwise an agent sends the update. We check what your system can do before building any automatic alert.

Payments stay on your gateway. The chat carries the link and the money moves on the gateway's page. Gallabox documents hosted checkout links from Network International for the Middle East, and any other gateway works as a plain link. There is no built-in KNET, MyFatoorah or Tap Payments integration, so payment confirmations depend on a webhook we set up.

And a bot is not a travel agent. It can collect a brief, send a checklist and answer the questions you have written answers for. A changed booking that involves money, a visa refusal or a missed flight belongs with a person.