E-commerce
August 2, 2026
Before returning a product, the customer wants to know if they are eligible for a return. The answer often depends on the timeframe, condition, type of product, proof of purchase, accessories, and policy exceptions.
The chatbot must verify these criteria without promising a refund too quickly. It explains what is confirmed, what must be inspected upon receipt, and when human validation is required.
This guide shows how to use an AI chatbot to verify return eligibility in a clear and fair manner.
Summary
Why must return eligibility be explained?
A customer may believe that any product can be returned in all cases. However, some items are personalized, used, incomplete, hygienic, perishable, or past the deadline.
The chatbot must avoid surprises: it explains the criteria before the customer prepares the package or expects an automatic refund.
Verifying return eligibility means clarifying the rule before initiating the logistics.
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 accessories, the packaging, the evidence, and the product category.
It must also ask if the product has been used, installed, customized, washed, opened, or damaged, as these elements can change the response.
How to explain the criteria?
The criteria must be formulated simply: deadline still valid, complete product, acceptable condition, returnable category, and proof of purchase available. If a criterion is missing, the bot must explain which one.
It must differentiate between apparent eligibility before sending and final validation after receipt or inspection of the product.
This nuance is important, because the customer can obtain a label while remaining subject to the inspection of the returned product. The chatbot must therefore explain that initiating the return does not constitute final acceptance of the refund.
How do you handle exceptions?
Some returns require validation: defective product, gift, preparation error, professional order, personalized item, opened product, or out-of-time cases.
The chatbot can collect the details, but it must not decide on a commercial exception or warranty on its own.
How to guide towards the right solution?
If the product is eligible, the bot can explain the return method, label, drop-off, tracking, and refund timeframe. If eligibility is uncertain, it can prepare a support ticket.
If the problem is rather a matter of after-sales service, the chatbot must direct to a defect or warranty claim instead of a classic return.
When several solutions are possible, the bot must present the one best suited to the reason. An exchange can correct a size, while after-sales service is more relevant if the product does not work properly.
Which flow to follow?
The flow must verify the criteria before starting the return.
Identify the order, product, receipt date, condition, and reason.
Verify the timeframe, category, accessories, packaging, usage, and proof of purchase.
Explain apparent eligibility, missing criteria, or required inspection.
Direct to return, exchange, after-sales service, or transfer depending on the situation.
Transfer exceptions, defects, out-of-timeframe cases, personalized products, and disputes.
Which messages should be used?
To verify: "I am going to check the main criteria before initiating the return."
To limit: "The return seems possible, but final validation will depend on the inspection upon receipt."
For exception: "Since this product is personalized or past the deadline, I must forward it for verification."
When to transfer?
Transfer is necessary if the product is overdue, customized, defective, incomplete, used in an uncertain manner, linked to a warranty, or if the customer disputes a rule.
The bot must transmit the order, product, deadline, reason, condition, photos, proof of purchase, blocking criterion, and exact request.
Which KPIs should be monitored?
Track eligibility checks, initiated returns, refusals, exceptions, redirected after-sales service files, missing proof, and disputes based on criteria.
This data shows whether the return policy is understood before the package is sent.
Which mistakes should be avoided?
Avoid promising a refund before inspection, ignoring an excluded category, initiating a return for an after-sales service defect, or refusing an exception without gathering proof.
The chatbot must apply the policy with clarity and empathy.
How can Qstomy help?
Qstomy can connect the chatbot to store stock, shopping carts, retail events, orders, return policies, and refund statuses to answer clearly, then transfer sensitive cases with an actionable summary.
The chatbot helps the customer move forward without inventing a availability, reservation, eligibility, or refund 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
Return eligibility must verify timeframe, condition, category, accessories, proof, and exceptions.
What the customer must understand
The customer must understand what is possible before sending and what will be validated after inspection.
The appropriate limit of the chatbot
The chatbot can initiate simple returns, but it must transfer defects, out-of-timeframe requests, custom items, warranties, and disputes.
Enzo
August 2, 2026
