# Chatbots for returns and exchanges: guide each request clearly

> Connect returns and exchange chatbots to orders, current policies and inventory, and clearly explain request, inspection and refund stages to customers.

_Mustafa Kuru — Kıdemli Yazılım Geliştirici · 2026-08-15 · https://palmate.ai/blog/chatbots-returns-exchanges_

A returns chatbot can collect a request, find the order, explain requirements and start supported actions. It needs current store policies and suitable system connections. Receiving a request, inspecting an item and completing a refund are different stages. Explaining exactly where the customer stands is as important as responding quickly.

## Key Takeaways
- Distinguish a return request from a completed refund.
- Verify stock and action results during exchanges.
- Keep human support accessible for exceptions and disputes.

## Turn policy into usable rules
Clarify conditions, product groups, exchange options and exceptions with operations. Do not treat store policy as overriding applicable consumer rights. For uncertain cases, define an authorised handoff instead of generating a definitive rejection.

## Verify the order and item
Match the customer to the order and clarify the item, quantity and reason. For multi-item orders, do not mark everything returned because one item is involved. Check delivery and previous requests in the [connected store system](/integrations).

## Show the next step
Create a request or shipping code if supported; otherwise route to the approved application process. Verify the result before claiming a code or request exists. Explain packing, sending and tracking steps clearly.

## Check stock and price for exchanges
A new size or colour requires current inventory. Allocating a replacement is different from seeing it in stock. Explain any price difference and required approval. If stock disappears, offer alternatives or human help without losing the original request.

## Separate inspection and refund status
“Request received,” “item received,” “under review” and “refund completed” are separate stages. A store initiating a refund and the bank showing funds are different events. Do not promise an unverified payment date. Route damage, missing-item cases and disputes to agents.

## Evaluate your own workflow
Explore [the e-commerce chatbot](/ecommerce-chatbot). [Request a demo](/contact) to review the flow with your own systems and customer requests.

## Frequently Asked Questions

### Can the chatbot resolve every return?
It can proceed only within defined rules and supported actions. Exceptions and disputes need human assessment.

### Are shipping codes created automatically?
That depends on whether the store or logistics integration supports the action.

### How should satisfaction be measured?
Track repeat contacts, incorrect routing, completion time and customer feedback together.