Question handling

Answering refund questions without promising the refund

Almost nobody types the word refund because they want a definition. They want to know two things: whether their case qualifies, and how many days until the money is back. An assistant can answer both honestly from your own policy, and the moment it goes further than that it has committed your business to something nobody approved.

What they are really asking

Am I going to get my money back, and if so, how long before it is actually in my account.

  • i want a refund
  • how long does a refund take
  • can i get a refund if i changed my mind
  • is this refundable
  • my refund hasnt arrived yet
  • i was charged twice
  • do you refund the delivery cost
  • can i have a refund instead of a credit note
  • how do i get my money back

The material that answers it

An assistant is only as good as the document behind it, and for this question the document usually exists but is written in the wrong shape. What each one has to contain to be answerable:

Material that answers this question
Your refund policy, written as conditionsNot a paragraph of reassurance. A list: what qualifies, what the window is, what condition an item has to be in, what is excluded, and whether shipping comes back. An assistant can only be precise if the document is, and most refund policies are written to sound generous rather than to be applied.
The statutory rights wording you already publishIn many markets a seller has to state that its own policy sits on top of legal rights rather than replacing them. Index that wording verbatim, because it is the sentence that stops the assistant quoting a policy exclusion at somebody who has a right the policy cannot remove.
Refund timing from your payment providerTwo separate clocks: how long you take to approve and issue, and how long the money then takes to appear. Write both, and write that the second clock starts at issue rather than at request. This one fact removes most of the follow up messages.
Worked examples of the cases you actually seeChanged mind, wrong size, arrived faulty, duplicate charge, subscription renewed unnoticed. Each with the outcome and the route. Examples index far better than abstract policy clauses, because customers describe their situation rather than naming a clause.
What happens after a refund is requestedWho reviews it, how the customer is told, and what the confirmation looks like. The assistant cannot approve anything, so the useful thing it can supply is an accurate picture of the next step and who takes it.

How to handle it

Separate eligibility from approval, in that order

Eligibility is a published fact: your policy says purchases of this kind, in this condition, inside this window, qualify. The assistant can state that, with a citation, all day long.

Approval is a decision about one order that somebody at your business makes. The assistant has no visibility of the order and no authority over the decision, so the sentence it must never produce is any variant of yes, that will be refunded. State the rule, then say that the team confirms against the order.

Answer the timing question with both clocks

The single most repeated refund message is a chase, sent by somebody who was told a number of days and started counting from the wrong event. Your review time and the card or bank settlement time are different clocks, and the second one is not yours.

The honest reply names both: how long you take to process, then the range the payment provider gives for the money to land, and the fact that the second range begins when the refund is issued. Say clearly that a refund usually returns to the original payment method, because a surprising number of people expect a bank transfer.

Name the exclusion before the customer finds it

Perishables, personalised items, unsealed hygiene products, downloadable content already accessed, services already delivered. If your policy excludes something, the assistant should surface that in the answer rather than describing a smooth process the customer will be ejected from later.

An exclusion delivered up front reads as clarity. The same exclusion delivered after somebody has posted an item back reads as a trick, and that is where the complaint comes from.

Close by taking the case, not by closing the conversation

A refund conversation that ends with a policy quotation and nothing else has moved nobody. When somebody asks for a person, the assistant offers the contact form and collects a name, an email and their message, which arrives at whichever address you nominate.

Tell the customer what to include: order reference, what they bought, and what is wrong. A refund request that arrives with those three things is handled in one reply instead of three.

When it stops being an answer

Any refund that has not been approved

This is the hard line. The assistant may say a case looks like the sort of thing the policy covers and that the team will confirm. It may not say the refund is approved, is being processed, or is on its way, because it has no way to know any of those and the customer will quote the sentence back.

Anything that sounds like a dispute or a chargeback

Words like unauthorised, fraud, my bank, or dispute change the nature of the conversation. Card schemes run their own dispute processes with their own deadlines, and a customer who raises one has started a clock the business needs to know about immediately.

Route these to a person straight away with the details captured, rather than answering from a policy page that has nothing to say about scheme rules.

Faulty goods wearing the clothes of a refund request

In many markets a fault triggers statutory remedies that exist independently of a shop's own returns policy, and they can be wider than the policy and last longer than its window. An assistant that answers a fault with the standard returns window is quoting the wrong rule.

Configure the material so faults are recognised as a distinct route, and let a person handle the remedy.

How this one goes wrong

The refund the assistant promised and the business refused

It happens the same way every time. Somebody describes a situation that sounds like it qualifies, the assistant reaches for the most encouraging passage in the returns page, and produces a sentence that reads as a commitment. The customer screenshots it.

What it costs is not the refund. It is the argument afterwards, in which your own support tool is the evidence against you, and the customer is right to be angry because they were told. Cautious matching and a policy written as conditions rather than reassurance are what prevent it. So is a refusal message that says plainly the team confirms every refund against the order.

The same question, trade by trade

The pattern above holds everywhere. The wording, the escalation line and the material behind it do not, so there is a page per trade.

Questions

Can it tell somebody whether their specific refund has been processed?
No. It answers from documents you index, and no document contains the state of one person's order. Unless you separately connect a data source that holds that information, it should say so and take the details for the team rather than guessing.
How do we stop it being too generous?
Two things. Index a policy written as conditions rather than as marketing, and raise the caution setting so it refuses on a weak match instead of reaching for the nearest encouraging paragraph. Every answer carries a citation, so you can see exactly which passage produced a reply you did not like.
Is it safe to publish the refund timing at all?
It is safer than not publishing it. The chase message exists because nobody was told which clock they were counting on. State your processing time, state the provider's settlement range, and say which event starts the second one.
What about refunds on subscriptions somebody forgot to cancel?
That is a policy decision rather than a configuration one. Decide what you actually do, write it down, and index it. An assistant that has no answer for the most predictable refund request you get is not the problem; the missing policy is.

Keep reading

Try it on your own material

Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.