WhatsApp Business API for delivery and logistics, where a pin beats an address

In delivery, WhatsApp is a cost-control tool. Every message that prevents a failed trip pays for itself; every message that only says 'your parcel is on its way' is a charge you could skip. These four flows earn their place.

Location first. Trigger: a new order or shipment is created in your system. Message: a utility template with the order number, the expected day and a request to share a location. Reply: the customer sends a WhatsApp location pin, and it is written back to the order through the API. Handover: if the pin falls outside your coverage, or the customer types an address instead, a dispatcher checks it before the route is built.

Cash-on-delivery confirmation. Trigger: an order is marked COD and ready to dispatch. Message: the amount due, the delivery window and two buttons — confirm or change. Reply: a confirmation releases the order to the route; a change opens the reschedule flow. Handover: customers who haven't answered by cut-off go to a calling list rather than onto a van.

Reschedules and failed attempts. Trigger: a driver marks a delivery as failed, or the customer taps 'change'. Message: the next available slots as a list. Reply: the customer picks one, and the new slot goes back to your system. Handover: a second failure goes to a person, with the driver's note attached.

Proof of delivery and business shipments. Trigger: the driver closes the job. Message: a delivered notice with the time, the receiver's name and, if your driver app captures them, a photo or signature. For business accounts, the same events feed status updates to the named contact at the client, plus an alert when a shipment is held. Handover: a dispute over a delivered parcel goes to customer support with the proof already in the thread.

Almost everything a delivery company sends is a utility template: order created, out for delivery, delivered. Until 30 September 2026 each costs $0.0091 to a Kuwaiti number, and replies inside the 24-hour window are free. From 1 October 2026 Kuwait becomes its own market, utility rises to $0.044, and it is charged even when the customer wrote to you minutes earlier. Gallabox adds 15% to Meta's rate.

That is the highest utility price in Meta's GCC table from October: Saudi Arabia is $0.0107, the UAE $0.0157, Qatar $0.012, Oman $0.0247, and Bahrain, still in Rest of Middle East, $0.0091. Meta prices each message by the recipient's country code, so the same shipment update costs a different amount depending on whose phone it reaches.

The practical answer is to cut messages, not information. Drop the 'order received' note if the pin request can carry the order number. Merge 'out for delivery' and the driver's contact into one template. When a customer has just messaged you, answer with a normal reply: service replies use 1,000 free messages per number each month before $0.044 applies.

If you use a one-time code at the door, check whether it fits Meta's authentication category — fixed wording built for passcodes — or belongs inside a utility update. In Kuwait both cost $0.044 from 1 October, so choose on format, not price. At volume, Meta's tiers lower the rate once a business portfolio passes 100,000 utility or 300,000 authentication messages in a month, counted per market.

Kuwaiti addresses are precise on paper — area, block, street, avenue, house — and still hard to find at night in a new district. Asking for a pin in the first message, before the route is planned, removes the phone call from the doorstep.

Some customers will send their PACI address number instead of a pin. The bot should accept it as a fallback, store it on the order and still ask for a pin: the number helps the office, the pin helps the driver.

Cross-border GCC work adds a second layer. A shipment from Kuwait to Riyadh has a sender on a Kuwaiti number and a receiver on a Saudi one, priced differently, and possibly a customs hold in between. The flow should tell each side only what they need, in the language they chose, and route held shipments to the team that handles clearance.

Timing shifts through the year. Friday and Saturday windows, Ramadan evenings after iftar, and summer afternoons when a parcel shouldn't be left outside a door all belong in the slot list the reschedule flow offers. Those rules live in your system; the bot only presents them.

Drivers need the same care as customers. A dispatcher who can see every driver's chat in one inbox, tag it by area and leave an internal note sorts out a wrong gate or a locked building without three phone calls.

The deciding factor is the API. Basic ($112 a month billed yearly) includes Gallabox's message and contact API at 100 messages a minute, with 3 users and no more. That works for a store running its own deliveries at modest volume.

Essential ($248 a month billed yearly) opens the full API at 200 messages a minute, 6 users with extra seats at $18, custom inbox views for dispatch, and team management. Most courier and last-mile operations start here.

Advanced ($474 a month billed yearly) raises the API rate to 1,000 a minute — which matters when a morning dispatch wave fires a large batch of pin requests at once — and adds 10 users, custom roles and 100 active flows. Enterprise sets the rate and seats by quote. Broadcast limits of 10K, 500K and 1M contacts a month matter less here than the API rate, because delivery messages are triggered one at a time.

Setup through Aahfil is free: connecting the number, preparing business verification (Meta decides the outcome) and the first templates. You pay the Gallabox plan and Meta's message fees.

Gallabox has no built-in integration with couriers operating in Kuwait; its ready-made shipping connectors are for Indian carriers. Everything on this page runs on events your order, warehouse or transport system sends through the Gallabox API or a webhook. If your system can't send events, we build a small bridge, or dispatchers work from the inbox.

Messaging limits apply from day one. A new business portfolio can start conversations with 250 unique people in a rolling 24 hours. Verifying the business, or delivering 2,000 high-quality templates to unique users within 30 days, lifts that to 2,000, and it climbs to 10,000, 100,000 and then unlimited as you use at least half of it with good quality. A launch with more customers than your limit needs planning.

WhatsApp doesn't collect cash-on-delivery money or card payments in Kuwait. A prepay link from your gateway can go out instead, and no bot can make a customer answer: an unconfirmed COD order still needs a phone call or a hold rule.