E-commerce
June 26, 2026
A product return is not always a simple refund request. The customer may want to exchange a size, report a defect, request a repair, return a gift, or understand why their return is not accepted.
The chatbot must guide the customer to the correct path: exchange, refund, after-sales service, or human review. It explains the conditions, collects useful evidence, and avoids promising a decision before verification.
This guide shows how to use an AI chatbot to make returns and exchanges clearer, without creating unnecessary frustration.
Summary
Why do returns need to be qualified?
Two customers can say "I want to return this product" for very different reasons: wrong size, damaged product, ordering error, disappointment, incompatibility, or breakdown. The processing depends on the reason.
The chatbot must therefore understand the situation before offering a label or a refund. Incorrect routing can extend the delay and worsen frustration.
A good return starts with the right reason, not with a generic form.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
What information should be requested?
The bot must verify the order, the product, the receipt date, the condition, the reason, the photos if necessary, the customer's wish, the presence of accessories, and the applicable return conditions.
It must also distinguish between a standard, custom, consumable, installed, used, or potentially defective product. These details change the eligibility.
How do I choose between an exchange and a refund?
If the customer likes the product but not the size, color, or variant, an exchange may be more appropriate. If the product does not meet the need or if the desired variant is unavailable, a refund or store credit may make more sense.
The chatbot must explain the available options and their timeframes, without steering the customer against their interest.
How do I manage a defect or a breakdown?
A defect, breakdown, or damage upon receipt must not be treated as a standard return. The bot must request a description, photos, the context, and the impact on usage.
It can prepare an after-sales service file, but it must not make a decision on its own regarding the warranty, replacement, or refund.
How can the delays be explained?
The customer must know when to drop off the parcel, when the return tracking is activated, when the inspection will take place, and when the refund, exchange, or repair can begin.
A clear timeline reduces follow-up inquiries. The bot must specify what depends on the carrier, the warehouse, or the customer service team.
Which flow to follow?
The flow must direct to the correct treatment from the start.
Identify order, product, reception date, condition, and reason for return.
Check eligibility, exceptions, timeframe, accessories, and required proof.
Offer exchange, refund, store credit, or after-sales service depending on the situation.
Explain label, drop-off, tracking, inspection, and resolution time.
Transfer defects, warranties, exceptions, sensitive products, and disputes.
Which messages should be used?
To qualify: "I am first going to check the reason for the return to guide you to the right solution."
For exchange: "If only the size is not suitable, I can check the availability of another variant."
For after-sales service: "Since you are reporting a defect, I am preparing a file with photos rather than a standard return."
When to transfer?
The transfer is necessary if the product is defective, out of time, personalized, used, incomplete, linked to a warranty, or if the customer disputes a return decision.
The bot must transmit the order, product, reason, condition, photos, timeframe, desired solution, apparent eligibility, and exact question.
Which KPIs should be monitored?
Track return reasons, successful exchanges, refunds, after-sales service cases, rejected returns, missing evidence, processing times, and second returns after exchange.
This data shows whether product descriptions, size guides, and return policies are truly reducing purchasing errors.
Which mistakes should be avoided?
Avoid proposing a refund before inspection, treating a defect as a simple withdrawal, ignoring missing accessories, or hiding processing times.
The chatbot must make the return predictable, not artificially accelerate an uncertain decision.
How can Qstomy help?
Qstomy can connect the chatbot to orders, return policies, product sheets, traceability data, take-back programs, tutorials, and customer service to answer clearly, then hand over sensitive cases with an actionable summary.
The chatbot helps the customer move forward without inventing an eligibility, proof, diagnosis, or decision that has yet to be confirmed by a reliable source.
Explore AI support, the AI sales agent, or request a demo.
Key takeaways
Key takeaways
A product return must be categorized according to its reason, condition, timeframe, and the desired solution.
What the customer must understand
The customer must understand whether they qualify for an exchange, refund, store credit, or after-sales service claim.
The appropriate limit of the chatbot
The chatbot can guide simple returns, but it must transfer defects, warranties, exceptions, and disputes.
Enzo
June 26, 2026
