Send a verified status from your order system and keep the message focused on the existing purchase.
1. Identify the actual change
Choose one event: payment confirmed, parcel dispatched, pickup ready, or a delivery delay. Prepare the order reference and the time of the last status check. Obtain permission for order messages. Do not turn every internal processing step into a notification if it changes nothing for the customer.
2. Explain the next step
Tell the customer whether to wait, collect, track, or contact support. Distinguish an estimated delivery date from a guaranteed commitment. If a delay has no confirmed resolution, say when you will provide the next update rather than inventing a delivery day. Keep cross-selling out of this operational message.
3. Validate links and recipients
Check that the tracking destination matches the order and works on mobile. Exclude cancelled or already collected orders. Tiringo can send a prepared campaign with custom fields, but it does not read live shop statuses. Refresh the source export before launching, and never send one customer another person’s tracking details.
4. Record the support outcome
Ask the support team to log unresolved deliveries, incorrect references, and repeated questions in the order system. Delivery and read statuses do not prove that the parcel arrived. Start with one clearly defined order event, check replies, and compare the message with the actual fulfillment record.
5. Prepare for an incorrect status
If a customer says the parcel arrived while your message reports a delay, check the carrier and order history before answering. Acknowledge the mismatch and correct the source record. Do not simply repeat the exported status. A short exception procedure prevents an automated-looking conversation from becoming an unresolved support issue.
- Verify the order reference first.
- Check the latest fulfillment record.
- Correct the source before the next send.
