Delivery notifications are customer messages tied to a meaningful change in an order’s shipping journey. Design them as an operational sequence: a verified event, an appropriate recipient, a useful explanation and an owner for the next action. Prepare the sending rules and the difficult cases alongside the message copy.
Define what deserves a message
Create a trigger list for shipment confirmation, out for delivery, completed delivery and exceptions needing attention. For each trigger, name the source event and what the customer learns. Keep routine scans in the tracking history when they add no useful action. Confirm whether a shipment confirmation means preparation has started or the carrier has physically received the parcel.
Write the fact and the next action together
Include a recognizable order reference, the affected parcel when an order is split, the confirmed change and one tracking destination. Separate information from instructions. An address query might ask the customer to contact support; a customs review might require an internal investigation. Do not ask customers to act when the next step belongs to your team.
Decide language and repeat-event rules
Choose the source of the customer’s language and communication preference, plus an explicit fallback when either is missing. Review applicable messaging requirements with the people responsible for them. Define how repeated or late events are handled before enabling delivery. A second copy of an event should not restart the same communication sequence or send an outdated status after a newer update.
Plan what happens when a message fails
Give missing contact details, broken tracking links and failed sends a review path. Test a sample sequence in order, including a split shipment and an exception. Check that subject, body, destination and support language agree. Record the event and template involved when reviewing a complaint, so the team can distinguish a wording problem from an unreliable trigger.
Notification launch checklist
When considering JetonTrack, confirm available channels, event handling, delivery monitoring and configuration responsibilities with the team.
- Approve one customer purpose and source event per trigger.
- Preview missing fields, duplicate events and late updates.
- Check parcel context, language fallback and the help route.
- Name the owner of failures and customer replies.
- Review a complete sample sequence before approving rollout.
Common questions
Should we notify customers after every carrier scan?
Use the customer’s need to decide. A scan that changes neither the delivery explanation nor the next action can remain in the tracking history.
How should a message describe a delay?
State the known event, explain who is checking the issue and provide a help route. Use a new arrival estimate only when a reliable source supports it.