WhatsApp Delivery Notifications for Couriers & Fulfillment Teams

Delivery teams live in a loop: pack the order, hand it to a driver, then spend the rest of the day fielding "where's my package?" calls. Email tracking links get ignored — open rates hover around 20%. WhatsApp messages get read within minutes, which makes it the better channel for anything time-sensitive like a delivery window or a failed drop-off.

This guide covers which delivery events are worth messaging, how to wire them up from a dispatch or fulfillment system, and how to stay GDPR-compliant while doing it.

The four moments that matter

Not every scan event needs a message. Four moments cover almost all of the "where is it" traffic:

1. Dispatched. The order left the warehouse or store. Include the order reference and an estimated delivery window, not just a date.

2. Out for delivery. The single highest-value message for home deliveries — it tells the recipient to expect the driver today, often with a narrower time slot if your routing system provides one.

3. Delivery attempt failed. This is where WhatsApp beats email outright: a failed-attempt SMS or email often isn't read until it's too late to act. A WhatsApp message with a reply option ("Reply 2 to reschedule for tomorrow") lets the recipient act immediately, and their reply can route straight back into your dispatch queue.

4. Delivered, with proof. A photo of the parcel at the door or a signature capture, sent as the final message. This also does double duty as your proof-of-delivery record for disputes.

What to skip: routine hub-scan events ("arrived at sorting facility") add noise without giving the recipient anything to act on. Save the channel for messages that change what the customer does next.

Wiring it up

Every dispatch or warehouse management system fires an event (webhook, queue message, or database trigger) on each status change. From there it's one HTTP call to the TextMeFlow API:

POST https://api.textmeflow.eu/v1/messages
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{
  "to": "+32470000000",
  "text": "Your parcel #A4821 is out for delivery today between 14:00-17:00."
}

For the proof-of-delivery message, attach a media_url instead of (or alongside) text — the API accepts images and PDFs up to 100 MB, so a driver-app photo or a signed delivery note both work without a separate document service. Full request/response fields are in the API documentation.

If your stack is a workflow tool rather than custom code, the same event can trigger a n8n, Make or Zapier scenario — useful when dispatch runs on a TMS or WMS you don't want to touch directly.

Handling replies without losing them

A "reply 2 to reschedule" message only works if replies actually reach a human or a system that acts on them. Incoming messages arrive at your endpoint as HMAC-signed JSON webhooks — verify the signature, then route the payload into your dispatch queue or a shared support inbox. Since drivers and dispatchers often work from a single company number, note that multi-device support (letting ops and drivers both send from the same WhatsApp number) is available from the Business plan up.

Staying inside the rate limits

Fulfillment volume spikes around peak shopping periods, and it's tempting to blast every status update the moment it happens. TextMeFlow's anti-spam pipeline enforces per-plan rate limits, a risk score, automatic STOP-keyword handling, and quiet hours — so a batch of night-shift dispatch events won't wake anyone up or trip a ban. Design your integration to only call the four moments above and you'll rarely get close to the ceiling; see avoiding a number ban for the underlying mechanics.

GDPR: what to check

Delivery notifications are transactional, tied to an order the recipient placed — that's a straightforward legitimate basis, unlike marketing messages. Still: only send to the number the customer provided at checkout, don't reuse it for promotions without separate consent, and make sure your API provider offers a data processing agreement. TextMeFlow hosts in the EU (Paris) and issues a DPA automatically on paid plans. See GDPR and sending WhatsApp messages for the fuller picture. (General information, not legal advice.)

Start with one event

You don't need all four message types on day one. Wire up "out for delivery" first — it's the message with the clearest payoff in reduced support calls — then add the rest once you can see the effect on your ticket volume. The free plan (50 messages/month, no expiry) is enough to test the flow against real deliveries before rolling it out fleet-wide. Create a free account and your first delivery notification can go out today.