High volume

How logistics & delivery messages customers

01Real scenarios

Pickup confirmed

A notice the moment a shipment is picked up.

Out for delivery

A same-day notice with a live tracking link.

Failed delivery attempt

A notice explaining a missed delivery, with a reschedule option.

COD reminder

A reminder to keep cash ready before the rider arrives.

02Channel mix

Moment	Channel	Why
Pickup confirmed	SMS	Immediate, and needs no app at the pickup point.
Out for delivery	WhatsApp	Carries a live-location link and the delivery partner's contact in one template.
Failed attempt	SMS, with Voice for reschedule	A voice call for the reschedule when the SMS goes unread.
COD reminder	Voice	Confirms cash-in-hand before the rider is already at the door.

03Sector compliance notes

Each stage of a shipment's lifecycle needs its own approved template — bundling every update into one generic template is a common rejection reason.

Failed-delivery and reschedule messages need the underlying delivery attempt logged and available on request, or high-frequency sends can get flagged.

Voice broadcasts used for COD confirmation at scale need their own registered use case — routing them through an OTP-category voice line gets flagged.

Regional-language delivery updates, a real need outside metro areas, use Unicode encoding and split into more SMS segments, so plan message length for non-Latin scripts upfront.

04Template pack

Pickup confirmed

Your shipment #{{1}} has been picked up and is on its way to the hub.

Out for delivery

Your order #{{1}} is out for delivery, arriving today by {{2}}. Track live: {{3}}

Failed attempt

We attempted delivery of order #{{1}} but couldn't reach you. Reschedule here: {{2}}

COD reminder

Reminder: keep ₹{{1}} ready for your COD order #{{2}}, arriving {{3}}.

05Integration notes