WhatsApp for Logistics: What to Automate and How to Stay Compliant

Logistics runs on notifications nobody reads and phone calls nobody answers. WhatsApp fixes the read rate — but the reason it pays for itself is narrower than that: every failed first-time delivery you prevent saves a whole second trip, and a message costs a fraction of a cent.

Delivery-window notifications with a way out

The night before, send the window with three buttons: confirm, change the day, leave with a neighbour. The recipient answers in one tap and your route planning gets the change before the van is loaded rather than after it has been to the door. Drive it from the dispatch system through an automation and let a Flow collect a new slot when the answer is "not Tuesday".

Live status and location

Out for delivery, three stops away, arriving now. Where a doorstep is hard to find — an industrial estate, an unnumbered entrance, a rural address — location messages work in both directions: you send the driver's pin, or the recipient sends theirs and the driver stops circling. That is minutes per drop, and minutes per drop is the entire economics of last mile.

Proof of delivery in the thread

A photo of the parcel on the doorstep, a signature image, or a delivery code the recipient reads back. Because it lands in the same conversation as the notification that preceded it, the dispute evidence is already assembled when "it never arrived" arrives three days later — no cross-referencing between a courier app and a support ticket.

Inbound "where is my parcel?"

People will reply to the notification, so plan for it. An automated lookup on a tracking reference answers most of them without a human, with escalation to an agent for anything that is genuinely lost. This is deflection at the exact moment of anxiety, and it is far cheaper than the phone call it replaces.

The compliance note

Delivery messaging rests on contract performance rather than consent, which keeps things simple — but Meta's opt-in requirement still applies before you initiate, and if you are messaging on behalf of a retailer, the opt-in and the privacy notice should make your role clear. Set retention on proof-of-delivery media and location pins: they are personal data about someone's home, and keeping them indefinitely is harder to justify than keeping the delivery record. See the GDPR position on WhatsApp.

Why volume changes the vendor question

At a million notifications a month, a per-message platform markup is not a line item — it is a budget. Wholesale pass-through with a flat platform fee makes the cost curve flat where it used to be linear, and utility conversations are the cheapest category Meta sells. Run the numbers in the WhatsApp pricing guide. Owning the instance also means throughput and retention are yours to tune rather than a shared tenant's rate limit.