Writing a refund policy customers actually understand
A generated draft gets you most of the way. The rest is knowing what a clear policy needs, how to write it so it prevents tickets instead of causing them, and where the policy plugs into the way you handle support.
What a refund policy needs
A good refund policy answers the questions a customer has before they have to email you. Miss one and you get a ticket; cover them all and most people never need to ask. These are the parts almost every policy is built from.
How long someone has to ask. The single most-searched line in any policy — lead with it.
What state an item has to be in, or what counts as eligible. Vague here means disputes later.
Customer, you, or free over a threshold. People decide whether to bother based on this one line.
Any restocking fee and what can't be refunded at all. Say it up front, not after they've asked.
The exact step — an email, a form, a portal link. An answer with no next step generates a ticket.
Original payment method, how many days, and the bank-clearing caveat. Removes the "where's my refund?" follow-up.
Write it so customers don't open a ticket
Same policy, two ways of saying it. The first sounds reassuring and tells the customer nothing, so they email to find out. The second answers the question, so they don't.
The line in your policy
“How long does a refund take?”
The ticket-generating version
“Refunds are processed as quickly as possible. Please allow some time for the amount to be returned to your account.”
The version that ends the question
Approved refunds go back to your original payment method within 5 business days of us receiving the return. Depending on your bank, it can take a few more days to show up on your statement.
Six habits that make a policy land
A generated draft gets you about 80% of the way. These are the habits that close the gap, whatever you sell.
The number of days is the thing people came to find. Put it in the first line, not the fourth paragraph.
"You can return it within 30 days" beats "the buyer may, within the stipulated period, initiate a return." Write like a person.
"Within 5 business days" and "a 15% restocking fee" beat "promptly" and "a small fee." Numbers end arguments.
Final-sale and non-refundable items belong before checkout, not in the reply to an angry email.
An email, a form, a portal. One route, stated once, beats "contact us" with no destination.
Consumer rights vary by region, and this tool isn't legal advice. A quick professional read is cheap insurance.
Once your policy is written, it's only useful if customers can find it. Publish it as a help center article people can search, and let an AI agent answer “where's my refund?” from it automatically.
Refunds & your support workflow
A copy-paste policy is the right starting point. But a policy buried in a footer can't be searched, can't answer inside the chat widget, and goes stale the moment you change a term. Here's where the document ends and the workflow begins.
| Capability | Policy doc | Selvo Help Center |
|---|---|---|
| Writing the policy | ||
| Assembles a clear, copy-paste policy | ||
| Stays accurate when your terms change | Re-build and re-paste | Edit once, live everywhere |
| Covers the edge cases | Clause library to bolt on | Each its own article |
| How customers find the answer | ||
| Customers search the policy | ||
| Has its own shareable, linkable page | ||
| Answers "where's my refund?" in the chat widget | ||
| An AI agent answers from your policy 24/7 | ||
| Upkeep & cost | ||
| One place to update when a term changes | ||
| Shows you what customers actually ask | ||
| Price | Free | Included with Selvo |
