Delivery questions are predictable: where is the order, when will it arrive, can the address change, and what happens after a failed attempt. A clear Telegram menu collects the few details needed to answer without repeating the same questions.
The goal is a faster handoff to the person who can check the order, not an automatic promise that the parcel will arrive at a particular time.
Use four clear delivery routes
Separate order status, delivery time, address changes, and failed delivery. Add payment or pickup only when those topics are common enough to deserve their own button.
- Where is my order?
- When will it arrive?
- Change delivery address or time
- Courier could not deliver
Ask for the minimum useful data
Request the order number first. Ask for city or postal code when the delivery area matters. For an address change, collect the requested change but explain that the team must confirm whether the carrier can still update it. Never request full card details or account passwords.
Write replies that do not overpromise
State what is known, what the team is checking, and when the customer should expect the next update. If the courier estimate can change, call it an estimate. If another team owns the answer, keep the customer in the same conversation and update them after the handoff.
Keep ownership visible
One teammate should take the conversation while others can see the history. Separate Telegram topics prevent several delivery conversations from merging and help the next teammate continue without asking the customer to repeat everything.
Delivery triage table
Each route needs a minimum data set, a named owner, and wording that reflects what has actually been confirmed.
| Question | Ask for | Owner | Safe next step |
|---|---|---|---|
| Where is my order? | Order number | Support or fulfilment | Check the latest recorded status |
| When will it arrive? | Order number and city | Delivery coordinator | Give a confirmed window or label it as an estimate |
| Change address/time | Order and requested change | Delivery coordinator | Confirm whether the carrier can still change it |
| Failed attempt | Order and contact detail used | Support or carrier liaison | Check the attempt and explain redelivery or pickup |
Saved reply templates
Use these as a starting point and replace every bracketed field before sending.
“Thanks — we have order [number]. Its latest confirmed status is [status]. We will update you by [time] if the next scan has not appeared.”
“We recorded the requested change to [new address]. It is not confirmed yet; we are checking whether the carrier can update this shipment.”
“The original delivery estimate has passed. We are checking with [team/carrier] and will send the next update by [time], even if the status is unchanged.”
“The shipment shows a failed attempt on [date]. We are checking whether the next step is redelivery or pickup and will confirm it by [time].”
Implement the delivery flow in six steps
Start with the four common questions and one owner for each next action.
- Add the four delivery buttons to the first menu without hiding them behind a generic support option.
- Write the exact first question for each branch and remove fields that are not required.
- Assign support, logistics, or fulfilment responsibility for every branch.
- Create saved replies with placeholders for confirmed status, source, and next-update time.
- Test address changes and failed attempts because they require the clearest handoff rules.
- Review ten real conversations after launch and change the menu when customers repeatedly choose the wrong route.
Delivery conversation checklist
A teammate should be able to open the topic and understand the case without asking the customer to repeat it.
- Order number is visible in the conversation.
- The question type is clear.
- Only necessary address details were requested.
- Confirmed facts and estimates are labelled differently.
- One teammate owns the next update.
- The customer received a time for the next update.
- Carrier or fulfilment handoff is recorded internally.
- The final reply states the confirmed resolution.
Build the delivery support path