A Return Policy Chatbot That Doesn't Promise a Refund
A shopper asks, “Can I return this?” Your store's return policy may explain the conditions, but a helpful answer also needs to explain how to submit a request. It should not turn a general rule into a decision about that shopper's order.
For a store owner setting up Simple Agent, start with a narrow job: explain the published return conditions and point the visitor to the return-request process you already operate. Keep refund approval with that process. This guide walks through the source content, the questions to check, and the website handoff.
Keep the return conditions beside the request instructions
Open the policy customers can actually read on your store. Find the return window, when that window starts, item-condition requirements, exclusions, and the instructions for requesting a return. Include shipping costs or refund timing only if the policy states them. Missing details are questions for the person responsible for the policy, not gaps for the agent to fill.
Here is an illustrative source paragraph for a fictional shop, not a policy to copy into your business:
For eligible items, request a return within 30 days of delivery. Items must be unused and retain their original tags. Personalized items are excluded from this general return process. Submit a request through the Returns page linked from our Contact page. Our team reviews the order and confirms the next steps before you send anything back. For a damaged item or a question about an exception, use the same Returns page so our team can review your case.
The useful details are connected. The window begins at delivery, not the purchase date. A request is reviewed before the shopper sends an item back. A damaged item goes to a review route rather than being rejected automatically because it is not unused.
Replace every condition with your store's actual wording. Keep any applicable consumer-rights information intact; this exercise organizes an existing policy rather than writing legal terms. If two public pages give different return windows, resolve that conflict before adding them as sources.
Add the policy and the destination, not customer order records
The current Simple Agent getting-started guide describes URL, PDF, and direct-text sources. In a workspace with an active paid plan, add the public return policy and the page that explains how to request a return. Direct text can hold a concise FAQ prepared from those same approved rules.
Do not paste order exports, payment information, or customer conversations into this policy source. They are not needed to explain the general rules. A visitor asking about an individual order should reach the store's existing return-request channel, where your team can handle the relevant information through its normal process.
Open that destination yourself. Does the page have a working request form or a usable support route? Does the label match the instructions in the policy? An answer that says “visit our Returns page” is only useful when the shopper can find and use that page.
Adding policy text is not the same as connecting an order-management system. In this setup, the agent explains the process. It does not inspect a purchase, authorize a return, create a shipping label, or issue a refund.
Ask a normal question before checking exceptions
In the Agent Builder's Playground, begin with:
I received an unused item last week. How do I request a return?
For the illustrative policy, a useful answer would explain the window and condition requirements, then direct the shopper to the Returns page for review. It should preserve “request” and “review,” not say “your return is approved.”
Next ask:
Is the return window measured from when I ordered or when it arrived?
The answer should say delivery for this example, because that is what the source says. This is a small wording difference with a practical consequence: changing the starting point changes what the shopper believes they can do.
Finally, ask whether the store pays return postage. The illustrative source does not answer that question. A useful response directs the shopper to the return team for that detail without inventing a prepaid label or a shipping charge. If your actual policy does state who pays, check that the answer includes any conditions attached to that rule.
Check the questions that could create an accidental promise
Ask these separately rather than combining them into one long prompt:
- “My item was personalized. Can you approve an exception?”
- “The item arrived damaged. Do I still have to keep it unused?”
- “I sent a request. Has my refund been approved?”
- “Can you send my money back today?”
For the fictional shop, the first question needs the published exclusion and the review route, not a newly invented exception. The damaged-item question needs the specific case-review instructions. The last two questions need a clear statement that the shopper must use the existing returns channel for an order-specific decision or status.
Read the actual replies, not just whether they sound polite. Reject a reply that supplies an approval, refund date, label, or payment action unsupported by the source. Also reject a reply that treats the general policy as grounds to dismiss a damaged-item request without directing it to review.
If an answer is wrong, identify the exact sentence it should have used and clarify the source. Repeat that same question after the correction. Keep the question and expected boundary so a later policy edit can be checked against it.
Finish the handoff on the published website
After the Playground answers match your policy, follow the Embed instructions in the getting-started guide to install the widget. Ask the same return questions on the published store, including on a phone. Follow the suggested return-request link and check that the next step remains usable on the smaller screen.
The end of this conversation should be concrete: the shopper understands the published rule and knows where to request a decision. It should not end with a vague “contact support” if a specific returns route is available. Nor should the widget promise that merely sending a chat message has opened a return request.
When the policy changes, update the source and repeat the normal, exception, and refund-status questions. Keep the store page and the agent's answers aligned before advertising a new return condition.
To put this workflow on your store, gather the approved policy and a working return-request destination, then review the current Simple Agent paid plans and message allowances. The first useful scope is policy guidance with a reliable next step—not automated refund approval.
Ready to build your AI agent?
Guided setup in 90 seconds. One flat price, published monthly volume.
Create my agent