Constraints first
- One reply per tracking status; an agent must be able to pick the right one in five seconds.
- Each reply states what happened, what you are doing, what the customer can choose, and when they will hear next.
- Never blame the customer or name the courier unkindly; never promise a delivery date you cannot control.
- Email version under 120 words, chat version under 40.
- Placeholders in square brackets for order number, dates and names.
Inputs
- Store and what it sells: [e.g. a gifting store shipping sweets and hampers]
- Couriers used: [e.g. two national couriers and one local partner]
- What agents are allowed to offer: [e.g. reship, full refund, Rs 100 store credit, a free greeting card]
- Festival date that gifts are meant for: [e.g. Diwali, 8 November]
- Perishable items and their shelf life: [e.g. sweets 10 days]
- Escalation contact and hours: [e.g. team lead, 10 am to 7 pm]
Cover these statuses
- In transit with no update for three days or more.
- Out for delivery for two days or more.
- Returned to origin.
- Sent to the wrong hub or city.
- Marked delivered, customer says not received.
- Will arrive after the festival the gift was meant for.
Output format
For each status: a short name for the macro, the email version, the chat version, the options offered, and one line on when to escalate. Then a single internal checklist for agents on what to verify before sending any of them.






