Delivery Notifications for Logistics: WhatsApp and SMS Playbook

This guide is for operations, customer service and product leads at courier companies, third-party logistics providers and merchants running their own delivery fleets. It shows which delivery notifications to send, how to confirm addresses and cash on delivery (COD), and how to recover failed deliveries and returns with as little manual work as possible. Merchant-side order messages are covered in our ecommerce guide.

Which delivery notifications should you send?

Send messages at the moments a recipient can act or plan: before dispatch, on the day, and when the outcome is known. Hub-to-hub scans belong on a tracking page.

All of these are about a shipment the recipient expects, which fits Meta's utility description. Keep promotions out; see template categories.

How do you confirm addresses before dispatch?

Ask for confirmation whenever the address is incomplete, fails validation or belongs to an area with frequent failures. In many GCC cities, addresses rely on landmarks and building names, so a location pin and a reachable phone number save attempts.

Address confirmation template (utility)

Hello {{1}}, your {{2}} parcel is scheduled for delivery on {{3}}. Please confirm your address: {{4}}. Buttons: Address is correct | Change address | Share location

Procedure

1. Validate the address against your geocoding rules at order import.
2. Send the confirmation message for shipments that fail or fall into risk areas.
3. "Address is correct" marks the shipment ready for routing.
4. "Change address" or "Share location" opens a conversation in the dispatch inbox; recipients can share a location pin.
5. Agents update the shipment record with the new address or coordinates.
6. Unanswered confirmations trigger an SMS with a link, then a call for high-value parcels.
7. Hold or flag shipments still unconfirmed at route planning, according to your policy.

How should COD deliveries be confirmed?

Confirm the exact amount and payment options before the driver leaves, so the recipient has cash or a card ready and can cancel unwanted orders before an attempt is wasted.

Hello {{1}}, your {{2}} order will be delivered on {{3}}. Amount due on delivery: {{4}}. Payment: cash or card. Buttons: Confirm delivery | Reschedule | I did not order this

Route "I did not order this" to the merchant or fraud review before dispatch. Reconcile driver collections against confirmed amounts daily.

How do you recover failed deliveries?

Send a failed-delivery message immediately after the attempt, with the reason, the default next step and one-tap alternatives. The faster the recipient acts, the more likely the second attempt succeeds.

Hello {{1}}, we could not deliver your {{2}} parcel today: {{3}}. We will try again on {{4}} unless you choose another option. Buttons: Reschedule | Change address | Collect from point

Record each recovery action against the shipment. A recipient who does not respond should still get the default second attempt.

How should returns be communicated?

Returns need a pickup confirmation with the time window and packing instructions, then a confirmation when the return is received and when the refund or exchange is processed. The refund message usually comes from the merchant, so agree the event hand-off.

What compliance and channel considerations apply?

Recipients of parcels are often not the people who placed the order, and they may never have consented to messages from the courier. Agree with each merchant who collects consent, what the order form says, and which brand appears as the sender. See our opt-in guide.

• Data minimisation. Show partial addresses in messages and avoid listing parcel contents.
• Sender identity. Register SMS sender IDs where required; see sender ID registration.
• Fallback. Use Meta's sent, delivered, read and failed statuses to decide when to send SMS; see delivery status explained.
• Scam awareness. Fake "delivery failed, pay a fee" messages are common. Use consistent sender names, avoid fee requests by link where possible, and publish your official channels.
• Cost. Meta charges per delivered template by category and market; Meta's pricing documentation describes changes to utility and service message charging from 1 October 2026, so confirm in Meta's rate card.

Worked example: a Jeddah last-mile courier cuts repeat attempts

"Sahm Express", a synthetic last-mile courier in Jeddah, delivers for online merchants and handles a large share of COD parcels. Drivers lose time calling recipients who are not home or whose addresses are vague.

The courier now sends a WhatsApp address confirmation with a share-location option for shipments that fail address validation, and a COD confirmation with the amount on the evening before delivery. Out-for-delivery messages include a time window. Failed attempts trigger an immediate message with reschedule, change address and collection-point buttons.

Recipients not reachable on WhatsApp get SMS with a tracking link. Replies land in a dispatch inbox, where agents update shipment records. Sahm compares first-attempt delivery rate, COD refusals and calls per route with the months before launch, using its own data.

Common mistakes and honest limits

• Messaging every scan. It increases cost and teaches recipients to ignore you.
• Unclear sender. Recipients ignore messages from a courier name they do not recognise; include the merchant name.
• Buttons with no back-end action. Reschedule taps must change the route plan.
• No default next step. Silence should not mean the parcel disappears.
• Duplicate messages from merchant and courier. Agree who sends which event.
• Ignoring opening hours. Avoid late-night sends except time-critical delivery updates.
• Expecting messaging to fix addressing. It reduces failed attempts; it does not replace address data quality.

How OmniChannels.ai helps

OmniChannels.ai supports WhatsApp utility templates with variables and quick-reply buttons, phone preview and approval tracking, in Arabic and English. Scheduled campaigns on WhatsApp and SMS can be sent from an Excel or CSV upload of the day's shipments, with duplicate filtering. Recipient replies arrive in the Omni Inbox for dispatch agents. Channel fallback can switch undelivered WhatsApp messages to SMS, delivery reports with filters and CSV export identify failures, and dispatch systems connect through the public REST API and webhooks. See SMS or book a demo.