Out for delivery
SMSYour parcel {#var#} is out for delivery today. Rider {#var#}. Share OTP {#var#} only on receipt. Track: {#var#}Transactional. Keep the OTP warning in the text.
Logistics messaging keeps a customer informed at each handover: pickup, in transit, out for delivery, delivered or failed. The messages that matter most are the delivery-day ones, because they decide whether someone is home, has cash ready, and can be reached by a rider they have never met.
Most failed deliveries are communication failures. The address was unclear, the customer was out, or the rider called from a number they ignored. Small, well-timed messages fix a surprising amount of that.
CONNEX
SMS · Transactional
9:05 AM
4:40 PM
Confirm the booking, the pickup slot and the AWB number as soon as the shipment is created.
Send updates only on meaningful events such as reaching a hub or going out for delivery. A message at every scan trains customers to ignore you.
On the morning of delivery, send the rider’s first name, the delivery window and the delivery OTP. Route calls through a masked number so neither side shares a personal phone.
Confirm delivery with a receipt. If the attempt fails, say so at once, give the reason and let the customer reschedule with one tap.
Tell customers early when a shipment is delayed or returned, and how they can get a refund or arrange redelivery.
| Channel | Use it for | Why |
|---|---|---|
| SMS | Tracking updates, delivery OTP, failed-attempt alerts | Instant and universal. Handles burst traffic when many parcels go out at once. |
| Tracking links, address confirmation, reschedule | Two-way: customers can share a location pin or fix an address. | |
| Number masking | Rider and customer calls | Both parties call a virtual number, so personal numbers stay private. |
| Voice / IVR | Address verification and failed-delivery calls | Resolves address doubts quickly where messages go unread. |
Variables are written as {#var#}, the way they appear on a DLT template. Adapt the wording to your brand, then register it.
Your parcel {#var#} is out for delivery today. Rider {#var#}. Share OTP {#var#} only on receipt. Track: {#var#}Transactional. Keep the OTP warning in the text.
We could not deliver parcel {{1}} today ({{2}}).
What would you like to do?
[Reschedule] [Change address] [Call me]Utility template. A button beats a link for a fast reply.
Hi {{1}}, we need to confirm your delivery address for {{2}}. Please share your location or reply with the correct address.Send before dispatch to cut failed attempts.
Customers stop reading after the third message. Send updates on the events that change what they need to do.
It exposes both sides and leads to missed calls from unknown numbers. Use number masking and a consistent caller ID.
A prompt alert with a reschedule option saves more orders than any reminder campaign.
A short confirmation before dispatch avoids many failed attempts and returns.
A delivery OTP is a code the customer shares with the rider on receipt. It confirms that the right person received the parcel and cuts false delivery claims.
The rider and customer both call a virtual number that connects them, so neither sees the other’s real phone number. The link expires after the delivery.
Send updates on booking, pickup, out for delivery, delivered and failed or delayed. Skip minor scans, because too many messages reduce attention to the important ones.
Yes, using approved utility templates for customers who have opted in. It also lets customers reply with an address or location pin.
Yes. ConnexBetter routes high-volume bursts through transactional routes built for speed, and the API returns delivery reports for each message.
Tell us your daily shipment volume and courier set-up. We will map the messages that should fire at each event.