WhatsApp Business API for car dealers and garages in Kuwait

A dealership's WhatsApp traffic is really two businesses: selling cars and servicing them. The flows below cover both, and each follows the same shape — something triggers it, the customer gets one clear message, their reply moves it forward, and a named person takes over the moment judgement is needed.

Test-drive bookings. Trigger: a customer taps a Click-to-WhatsApp ad or the WhatsApp button on a model page. Message: the bot asks which model and which branch, then offers evening and weekend slots. Reply: the customer taps a time and receives a single confirmation with the date, the showroom's location pin and the consultant's name. Handover: any question about price, finance or stock goes straight to that consultant, with the answers already in the chat.

Service bookings. Trigger: a customer asks to book, or your service records show a car is due. Message: the bot collects the plate number, mileage and preferred day, and offers drop-off times at the nearest service centre. Reply: the customer confirms and gets a reminder the day before. Handover: anything beyond routine maintenance — a warning light, a strange noise, a warranty claim — goes to a service advisor.

Car-in-the-bay updates. Trigger: your workshop system changes a job's status. Message: 'received', 'estimate ready', 'ready for pickup', each with the job number. Reply: the customer approves the estimate with a button or asks a question. Handover: questions land with the advisor who owns the job. If your workshop software can call an API or send a webhook, these go out automatically; if not, an advisor sends them from the inbox.

Trade-in qualification. Trigger: a 'value my car' ad, or a customer mentioning a trade-in. Message: the bot asks for make, model, year, mileage and a few photos. Reply: the customer sends them in the chat. Handover: an appraiser gets a complete file and replies with a viewing time instead of a list of questions. Insurance and registration renewal reminders follow the same pattern once these four are running.

Meta charges per delivered message, and the price depends on the template's category. Until 30 September 2026, Kuwait sits in Meta's Rest of Middle East group: $0.0341 for marketing and $0.0091 for utility, with replies inside the 24-hour window free. From 1 October 2026 Kuwait is its own market — $0.0792 for marketing, $0.044 for utility — and Gallabox's rate card adds 15% on top.

Utility covers messages about something the customer already has in motion: a booked test drive, a car in the workshop, an estimate waiting for approval. From 1 October those are charged at $0.044 even when the customer messaged you in the last 24 hours. Inside an open window, a plain reply is the cheaper choice: service replies draw on 1,000 free messages per number per month before the $0.044 rate applies.

Marketing covers anything that sells: a new model launch, a service-package offer, an air-conditioning check before summer sent to everyone who bought a car from you. A 'your car is due, book now' nudge that nobody asked for sits close to that line, and Meta decides the category. It can reclassify a utility template as marketing, so we write reminders as reminders and budget offers at the marketing rate.

Ads change the maths. When a customer starts the chat from a Click-to-WhatsApp ad on their phone and you reply within 24 hours, every message for the next 72 hours is free, templates included. A test-drive or trade-in flow that finishes inside that window costs nothing in Meta fees.

Cars here are still bought in person. Customers compare on Instagram and ask on WhatsApp, but the deal closes in a showroom, often on a weekend visit with family. WhatsApp's job is to get the right person to the right branch at a time the consultant is there, which is why the booking flow offers Friday and Saturday slots first and the sales rota has to match them.

Service centres tend to sit in industrial areas such as Shuwaikh and Al Rai, where directions by block and street help nobody. Every booking confirmation carries the location pin for that specific centre, and the pickup message carries it again.

Language often splits the other way from what dealers expect. Customers start in Arabic, while many service advisors work in English. The bot asks for a language first and tags the chat, so Arabic conversations route to advisors who can reply in Arabic, and English ones don't wait in the wrong queue.

Summer matters too. Air-conditioning and battery checks before the heat are a natural campaign, but those messages are marketing, they count against WhatsApp's per-person marketing limits, and they should only go to customers who agreed to hear from you. On consent, Kuwait's CITRA Data Privacy Protection Regulation is the name to raise with your adviser.

A used-car showroom with two or three salespeople can run on Basic: $112 a month billed yearly, up to 3 users with no way to add more, and up to 5 active bot flows. That covers test drives and service bookings, and Basic's message and contact API is enough to push a status template from a workshop system.

Most franchised dealers end up on Essential, at $248 a month billed yearly. It includes 6 users (extra users $18 each), 20 active flows, drip campaigns for trade-in and finance leads that go quiet, business hours for the bot, the full Gallabox API, and the Conversions API link that tells Meta which ad chats turned into showroom visits.

Groups with several brands or branches look at Advanced ($474 a month billed yearly, 10 users, 100 active flows, custom roles and holiday schedules) or Enterprise, where seats and security are set by quote. Setup through Aahfil is free — connecting the number, preparing business verification for Meta to decide on, and the first templates — so the bill is the plan plus Meta's message fees.

Gallabox has no built-in connector for dealer management systems. Status updates and service-due reminders need your DMS or workshop software to call the Gallabox API or send a webhook, or a person to trigger them. We scope that link first, because it is usually the longest part of the job.

The chat doesn't take payments in Kuwait. A booking deposit or a service invoice goes out as a payment link from your own gateway, and a webhook from that gateway is what lets the chat confirm the payment. There is no built-in KNET connection.

The blue check is not part of the package either. Meta awards it to verified businesses with an approved display name, two-step verification and 30+ days on the platform, and even then nobody can promise it. And the bot should never quote a trade-in value or a finance approval: it gathers the facts, and a person makes the call.