A delayed parcel notification can arrive successfully and still leave the customer unsure what to do. Connect each update to the shipment's state, the next action and a route for questions.
Which channel should carry the update?
Choose a channel the recipient can receive and has permitted for the intended message.
Use SMS when the update needs text or a tracking link and should not depend on an installed messaging app. It still depends on a reachable number, network delivery and the applicable sending requirements.
Use WhatsApp when its availability and richer content fit the task. A photo, location or interactive response can keep more of the support exchange in the conversation.
Test the complete flow in each destination market. An available channel does not guarantee that your sender, recipient and content meet its requirements.
Keep recipient, courier and merchant communications distinct. Each audience needs its own relevant updates and reply routing. Permission from one person does not establish permission from another.
What should a WhatsApp delivery template contain?
Use approved wording for the shipment event and variables for details that change with each delivery.
A shipment update tied to an existing order can fit the utility category. Keep promotional offers separate rather than adding them to an operational notification.
Include enough context to identify the shipment and the next action. Supply tracking references, expected windows and links through the template's variables instead of authoring a template for every parcel.
Check the template language before sending. A template can be active because one language is live while another is unavailable.
Meta can classify a language differently from the category you declared. Compare the language's category and published pricing when estimating charges.
Fix rejected content through a new draft and follow that version's review. Do not assume that an earlier live version proves the replacement passed.
How should I handle replies and delivery failures?
Route replies to a shipment-aware support flow and choose fallback actions from the message's recorded outcome.
Answer routine tracking questions from the shipment record. Transfer address changes or unresolved exceptions to a person with the conversation history and shipment identifier.
Use a WhatsApp number that can receive customer replies. Bird-managed template senders do not provide that inbound support path. Configure your own number when replies are required.
Handle each channel's failure vocabulary. WhatsApp uses failed and rejected outcomes. An SMS handler also needs to handle undelivered and expired messages.
Do not wait for an event type the channel does not emit. Set your fallback policy around its documented outcomes and the notification's remaining usefulness.
Check permission and suppression before sending on another channel. Fallback must not bypass an opt-out.
What should I measure and store?
Keep shipment state separate from notification delivery, then measure delivery, replies, resolution and cost.
A delivered-message event describes the notification. It does not prove that a driver completed the delivery.
| Measurement | What it helps you investigate |
|---|---|
| Delivery by channel and market | Where notifications fail to reach recipients |
| Replies by notification type | Which updates generate questions or requested changes |
| Resolution without an agent | Which routine questions the shipment integration can answer |
| Agent handling | Which exceptions still need staff time |
| Cost per useful update | Whether the complete workflow justifies its sending and support costs |
A high reply rate can reflect useful engagement or unclear wording. Inspect the replies before deciding that the template is defective.
Store the shipment event identifier with the returned message identifier. Deduplicate repeated shipment events so processing retries do not create duplicate notifications.
Process webhook events using their identifiers and event times. Arrival order alone can overwrite a later message state with an earlier one.
For WhatsApp, separate Bird's platform charge from the Meta charge passed through in the message cost. Meta's message fees and your provider's charges have different causes.
What should I put in place before launch?
- Choose permitted channels that support each audience's destination and message content.
- Prepare the approved templates, variables and languages the shipment events require.
- Route customer replies to shipment data and an available support team.
- Deduplicate shipment events and define fallback without bypassing permission or suppression.
- Measure delivery, questions, resolution and total cost before increasing volume.
In short
Choose the channel for the recipient and task.
A tracking link and a delivery photo need different capabilities. Verify channel availability and permission before sending.
Prepare templates and their languages.
Use approved WhatsApp content when required. Check the language's availability and category before sending a shipment update.
Connect replies to the shipment.
Answer routine tracking questions from the shipment record and pass exceptions to a person with the conversation history.
Measure the notification's result.
Track delivery, replies, resolution and cost. A delivered message does not prove that the parcel was delivered.