WhatsApp chatbot for delivery updates
Most US recipients get delivery texts by SMS, but recipients abroad, cross-border shipments and customers who chose WhatsApp at checkout can get their updates there instead. A WhatsApp agent sends out-for-delivery and attempted-delivery messages, then handles the replies: leave it with a neighbor, deliver tomorrow, use the side gate.
How do logistics companies send delivery updates on WhatsApp?
Your dispatch or tracking system triggers a Meta-approved WhatsApp template at each stage, such as out for delivery or delivery attempted. When the recipient replies, the AI agent handles the conversation within the free 24-hour window: it records delivery instructions, collects a new preferred day, and answers questions from your service rules. Damaged, missing or disputed parcels go to a person with the thread attached.
Worked example
A day of replies to out-for-delivery messages
Say a courier sends 2,000 out-for-delivery templates on a weekday to recipients who opted in to WhatsApp, many of them on cross-border orders. The reply counts below are examples; your own will differ.
| Example reply | Count | What the agent does |
|---|---|---|
| "Leave it with number 12" | 60 | Records the instruction against the shipment through a webhook |
| "I'm not home, can you come tomorrow?" | 45 | Offers the next delivery days you allow and logs the choice |
| "Where is the driver now?" | 80 | Shares the status your system provides, without promising an exact time |
| "The box arrived crushed" | 6 | Asks for a photo and hands the thread to the claims team |
In this example, most replies never reach a call center queue, and the six damage cases arrive with photos already attached.
Setup checklist
What you need before the first template goes out
- WhatsApp Business API access after Meta business verification, which usually takes 24 to 48 hours.
- Approved templates for each event: out for delivery, attempted delivery, ready for pickup, delayed.
- A trigger from your system, sent through a webhook or Zapier, carrying the tracking number and recipient's name.
- Opt-in. Recipients must agree to receive WhatsApp messages, often captured by the shipper at checkout.
- Clear service rules the agent can quote: redelivery limits, safe-place options, hold periods at depots.
Meta charges per template; the recipient's replies and your answers inside 24 hours are free. Botcadence does not add a markup to Meta's fees.
For US recipients, SMS is the default text channel, so send US delivery texts there and offer WhatsApp as a checkout option. The same agent handles replies on both, in one inbox.
Boundaries
Where the agent stops
The agent does not approve claims, refunds or compensation; those go to your claims team. It does not invent ETAs it cannot see, so only connect fields your system knows. And it should not share delivery details with someone who is not the recipient; ask for the tracking number and ZIP code before discussing a parcel.
Shipper relationships
Whose name goes on the message
If you deliver for retailers, agree with each shipper whose brand appears in the template and who owns the opt-in. Some shippers want messages in their own name; others are happy for the courier's name to appear. Write that into the template set so a recipient always knows who is messaging them and why.
See logistics AI take a delivery exception report
Book a demo to map tracking questions or exception intake onto Botcadence with your service guide.
Common Questions
WhatsApp delivery update questions
Yes, within the options you allow. The agent offers available days from your rules, records the choice and passes it to your system through a webhook or Zapier so the route plan picks it up.
For most US recipients, SMS is the better default: it reaches any phone with no app to install. WhatsApp earns its place with recipients abroad, cross-border parcels and customers who picked it at checkout, and it handles photos of damage or a location pin for the door well. The same agent answers replies on both channels.
Templates are approved per language, so create one for each language you send in. Replies are different: the agent answers in the recipient's language across 50+ languages without extra templates.
The agent collects the tracking number, address and what the recipient sees, then hands the thread to your team with the full history. It does not decide whether a claim is accepted.
Start with tracking questions or exception reports
Begin with tracking questions and delivery-exception intake, then add proactive updates and rate-quote intake once ticket volume drops.
- Reader-first workflows
- Human handoff when needed
- Grounded in your content