Customer experienceNotifications

Delivery Notifications: WhatsApp & SMS Best Practices

By Routella Team··9 min read

The right delivery notification at the right moment prevents a support call, sets honest expectations, and makes a wait feel managed instead of mysterious. Get the timing and wording right and customers stop asking where their order is; get it wrong — too many messages, too vague, or sent too late — and you train people to ignore you. This guide covers what to send, when to send it, and which channel to use, with practical best practices for WhatsApp, SMS, and email.

Notifications are customer-facing and easy to overdo, so the goal is not "more messages." It is the smallest set of messages that keeps the customer informed at the moments they actually care about.

Which delivery notifications should you actually send?

For a local delivery with your own drivers, four messages cover almost every case. More than that and you start annoying people:

  1. Order confirmed. Reassures the customer the order landed and sets the expected delivery window. This is the message that prevents the first wave of "did my order go through?" questions.
  2. Out for delivery. The most important message of the day. It tells the customer to expect their order soon and should carry the live tracking link. Sent when the driver starts the route or reaches the stop before theirs.
  3. Arriving now / nearby. Optional but powerful for goods that need someone present — food, pharmacy, signature items. It gives the customer a few minutes to come to the door.
  4. Delivered. Closes the loop, ideally with proof of delivery attached. It confirms success and gives the customer a record.

Notice what is missing: a flurry of "your order is being prepared" updates. Those feel busy but add no information the customer can act on. The messages that matter are the ones tied to a real change in where the order physically is.

The "out for delivery" message is the one that earns its keep. It is the moment the customer starts wondering, and it is your chance to hand them a tracking link before they reach for the phone.

WhatsApp, SMS, or email — which channel for which message?

Each channel has a personality, and matching the message to the channel matters more than picking a single favorite.

  • WhatsApp — high open rates, feels personal, supports rich content and replies, and is the default in much of the world. Best for the "out for delivery" and "arriving" moments where you want the customer to actually see it. On Routella, WhatsApp is included on the Pro plan.
  • SMS — universal, works on any phone with no app, and gets read fast. The reliable fallback when you do not know whether a customer uses WhatsApp, and strong for time-sensitive alerts.
  • Email — best for the records customers keep: the order confirmation and the delivered receipt with proof attached. Weak for urgent "we are at your door" moments because it is not read in real time.

A common, sensible pattern: email for the confirmation and the receipt, WhatsApp or SMS for the live "on the way" and "arriving" moments. Routella can send all three from one place, so you choose per message rather than committing to a single channel.

When should each notification go out?

Timing is where most notification programs quietly fail. Send too early and the message is meaningless; send too late and the customer has already called.

  • Order confirmed — immediately, the moment the order is accepted.
  • Out for delivery — when the driver actually starts the route or is one or two stops away, not when you batch the route the night before. The link should go live with the message. Our live tracking guide explains why the timing of this one matters.
  • Arriving — a few minutes out, enough time to come to the door but not so early it is forgotten.
  • Delivered — at the moment the driver marks the stop complete, with the captured proof.

The thread that ties this together is the driver's actual progress. Notifications that fire off a guess go stale; notifications that fire off real route events stay true. This is also why optimizing the route first pays off in the inbox, not just on the road — see optimizing multi-stop routes.

What should a good delivery message say?

Short, specific, and human. A good "out for delivery" message names who it is from, says the order is on the way, gives a realistic window, and hands over the tracking link. It does not bury the link under three lines of marketing. Compare:

Weak: a generic "Your order status has been updated." It tells the customer nothing and trains them to ignore you. Strong: a message that says the order from your specific store is out for delivery, expected within the next hour, with a one-tap tracking link. The customer knows what to do with it.

Keep the link first and the words few. On a phone, a long message gets truncated and the tracking link can fall below the fold of the notification preview, which defeats the whole purpose. Lead with the one thing the customer needs — that the order is on its way and here is where to watch it — and leave promotions for another time. A delivery notification that doubles as an upsell reads as noise and gets muted.

Always identify yourself by name in the message. A text from an unknown number saying "your delivery is on the way" reads like spam; one that names the store the customer ordered from reads like service.

How do you avoid annoying customers?

Over-messaging is the fastest way to make notifications worthless. A few guardrails keep them welcome:

  • Cap the count. Four messages across the order's life is plenty. If you are sending six, cut two.
  • Deduplicate. Never send the same status twice because a route was re-saved. Each event should fire once.
  • Respect quiet hours. A "delivered" message at 6am is a complaint waiting to happen.
  • Make every message actionable. If a notification does not change what the customer should do or expect, it probably should not be sent.

How do I set this up without building it myself?

If you run your own drivers, you want notifications tied to real delivery events, not a separate tool you trigger by hand. Routella sends WhatsApp, SMS, and email automatically based on what the driver does — when a route starts, when a stop is reached, when it is marked delivered — so the customer gets the right message at the right moment without a dispatcher remembering to click anything. You can connect your store, and orders flow in ready to notify against. To wire notifications into your own systems instead, the developer docs cover the API.

Good delivery notifications are not a marketing channel — they are a service. Send the few messages that genuinely help, on the channel the customer reads, at the moment the order actually moves, and you will spend far less time answering the phone.

Frequently asked questions

How many delivery notifications should I send per order?

For a local delivery, four is usually the sweet spot: order confirmed, out for delivery, arriving (optional), and delivered. More than that risks training customers to ignore your messages. Each one should be tied to a real change in where the order physically is.

Should I use WhatsApp or SMS for delivery updates?

Use WhatsApp where it is common and you want the customer to actually see and possibly reply to the message — especially the out-for-delivery and arriving alerts. Use SMS as the universal fallback that works on any phone. Email is best for confirmations and the delivered receipt. Routella can send all three from one place, so you pick per message.

Do notifications send automatically or do I trigger them?

On Routella they send automatically based on real driver events — when the route starts, when a stop is reached, and when it is marked delivered — so a dispatcher does not have to remember to fire each one. That also keeps the timing honest, because the message follows the actual delivery instead of a guess.

Run your own deliveries with Routella

Route optimization, a driver app, proof of delivery, and live customer tracking — in one platform. Free plan, no credit card.

Keep reading

Live Delivery Tracking & ETAs: A Practical GuideHow to Reduce Failed Deliveries and Lift First-Attempt Rate