Customers who are home
Out for delivery messages read on WhatsApp change availability.
Fewer Failed Attempts,
Fewer Return Trips.
Most failed deliveries are a wrong address or an absent customer. A message they read, an address they can correct in chat, and a COD confirmation before dispatch prevent most of the second trips.
Delivery notificationsAddress correctionCOD confirmationFewer RTOs
Addresses fixed before the van
A correction in chat costs nothing. A failed attempt costs a trip.
COD confirmed up front
A yes or no before dispatch, not after the courier arrives.
Attempts
Every message that prevents a second trip
Dispatch, out for delivery, attempted and delivered each go out as utility templates. The attempted message includes a reschedule and an address correction option.
Replies land in a shared queue with the shipment context attached, so support answers with the tracking already in front of them.
- Dispatch and out for delivery notifications
- Address correction Flow in chat
- COD confirmation before dispatch
- Reschedule after a failed attempt
Deliveries · last 7 daysfailed attempts down 19%
StageCountRate
Dispatched24,180100%
Out for delivery23,94099%
Delivered first try21,10688%
Failed attempt2,83412%
COD confirmed before dispatch 96% · RTO down 14%4 templates
How it works
From zero to live,
in four steps.
01Wire your eventsDispatch, out for delivery, attempted and delivered, over the API.
02Confirm CODA yes or no reply before the parcel leaves.
03Let them correct the addressA Flow that updates the delivery address in chat.
04Reschedule failed attemptsOne tap to pick another day.
What is inside,
in detail.
Delivery notifications
Utility templates for each stage of the shipment.
Address correction
A Flow that captures a corrected address and pushes it back.
COD confirmation
Reply required before dispatch, recorded on the shipment.
Reschedule Flow
New date and slot after a failed attempt.
Shipment context
Tracking and status beside the conversation.
API triggers
Every message fired from your own systems.
What changes
With a platform,
and without one.
FeatureWith WBIZSMS and IVR
Notification read rateHighLow
Customer can correct an addressCall centre only
COD confirmed before dispatchRarely
Reschedule without a callNo
Cost per notificationMeta rate, at costPer SMS, plus markup
A comparison against running WhatsApp without a platform. See how WBIZ compares with other platforms.
Yes, over the API and webhooks. Any system that can post an event can trigger a message.
Yes, the Flow answer posts to your endpoint so your system can update the shipment.
Yes, that single message is where most RTO reduction comes from.
Yes, a Flow offers new dates after a failed attempt.
Explore more
The rest of the platform
Developer API
Trigger every notification from your own systems.
See the APIAutomations
The event driven sequences behind each stage.
See automationsWhatsApp Flows
Address correction and reschedule forms.
See FlowsCut failed attempts on your next thousand parcels
Start free, wire one out for delivery event, and measure the first attempt rate.