This guide is for online stores handling a customer’s product return, exchange, or refund after an order. It is not a guide to requesting a refund from Telegram or checking the status of a Telegram payment.
Returns become frustrating when the customer does not know what information to send or when the next update will happen. A good support workflow separates eligibility, return instructions, exchange, and the store’s refund update.
The bot should organize the request. A teammate still reviews the order and applies the store policy.
Create separate return routes
Use clear buttons for “Start a return,” “Exchange an item,” and “Refund status.” Link the published return policy so customers can read the rules without waiting, while still giving them a direct route for questions.
Collect evidence once
Ask for order number, item, reason, and photos only when they are relevant. Do not make every customer complete a long form. Keep documents and images in the same conversation so the next teammate can see what has already been provided.
Explain each next step
Confirm that the request was received, say whether it needs review, provide packing or shipping instructions after approval, and explain when refund processing starts. Do not describe a refund as completed until the business has actually issued it.
Use status messages consistently
A small set of saved replies keeps wording aligned: received, more information needed, approved, item received, refund issued, and request declined with the relevant policy reason. Personalize the details before sending.
Return and refund status model
Give every case one visible status. The label should describe the real step rather than imply approval too early.
| Status | Meaning | Customer update | Owner action |
|---|---|---|---|
| Received | Request and order number arrived | Confirm receipt and review time | Check policy and order |
| Needs information | A required detail is missing | Ask only for the missing item | Pause review without closing |
| Approved | Return or exchange is allowed | Send exact packing and shipping steps | Record deadline or label |
| Item received | Returned item reached the business | Confirm inspection or refund timeline | Inspect and record result |
| Refund issued | Business sent the refund | State date, amount, and payment route | Keep transaction reference |
Ready status messages
A status message should say what happened, what happens next, and when the next update is due.
“We received the return request for order [number], item [item]. We will check it against the return policy and reply by [time/date].”
“To continue, please send [specific missing detail]. We already have [details received], so you do not need to send them again.”
“Your return is approved. Pack [item], use [label/address], and send it by [date]. We will update you after it is received.”
“We issued [amount] on [date] to [payment route]. Your bank or provider may take additional time to display it.”
Implement the returns flow in six steps
Build the status model before writing automated messages.
- Publish the current return policy at a stable link and name the person who owns updates.
- Create separate menu routes for return, exchange, refund status, and policy questions.
- Define the exact evidence required for each product category instead of requesting everything from everyone.
- Add the five statuses to the team workflow and write the exit condition for each one.
- Test an approved case, a declined case, an exchange, and a delayed bank credit.
- Review closed conversations monthly for repeated questions that should be clarified in the policy or saved replies.
Returns QA checklist
Use the checklist before closing a conversation or handing it to another teammate.
- Order and item are identified.
- The applicable policy version is clear.
- Only relevant evidence was requested.
- Approval and refund completion are separate states.
- Shipping instructions include address or label and deadline.
- The customer knows the next update time.
- Payment data is not requested in chat.
- The final outcome and transaction reference are recorded.
Create a clearer online-store returns flow