New

Chatboq Ticketing System launching soon — Join the waitlist for early access

Chatboq

12 Live Chat Scripts for Handling a Refund Request

A chat conversation confirming a refund amount and timing

Template / Listicle Topics

Rachel Ong

September 25, 2026

Reading Time

6 minutes

Where the request clearly qualifies, approve it immediately and state the timing, since hesitation here creates doubt where none is needed.

1. Approved, within the window

That's within the returns window, so a refund is fine. I've started it now — [amount] back to your original payment method, showing within [timeframe]. Reference [number].

State the amount, the method and the timing together, since these are the three follow-up questions otherwise.

2. Approved, return required first

Happy to refund once we have the item back. Here's a prepaid label — post it whenever suits, and the refund goes out within [timeframe] of it arriving.

Being clear that the refund follows receipt, rather than implying it is immediate, prevents a chasing contact.

3. Approved, no return needed

No need to send it back. I've refunded [amount], showing within [timeframe]. Keep or dispose of the item as you like.

Used where return costs exceed item value, and worth stating explicitly since customers expect to return things.

Setting the timing expectation properly

Refund timing depends on the payment provider rather than on you, and saying so plainly prevents the customer chasing on day three.

Giving the outer end of the range, rather than the optimistic one, avoids a second contact when it takes longer.

Summarize this article with AI

ChatGPT

Perplexity

Claude

Table of content

Faulty and Damaged Items

Where the product failed, the customer should not carry any cost or effort, and the script should make that immediately clear.

4. Faulty on arrival

That shouldn't have happened. You've got a choice: a replacement out today, or a full refund including the original delivery. Whichever you'd prefer.

Offering the choice rather than defaulting to a replacement is what distinguishes good handling here.

5. Fault developed later

That's within the warranty period, so this is covered. I can arrange a repair, a replacement or a refund depending on [policy criteria]. Which suits?

Where the policy limits the options by age or fault type, say so rather than offering choices that will then be withdrawn.

6. Fault outside warranty

This one's outside the warranty period, which means a free replacement isn't something I can do. I can arrange a paid repair at [cost], or [alternative].

Offering a paid route converts a declined claim into a service outcome rather than an ending.

Outside Policy

Declining needs to be clear, reasoned and accompanied by whatever alternative exists, since a bare refusal produces escalation almost every time.

7. Just outside the window

You're [duration] past the returns window. I can't process this as a standard return, but given [circumstance] I'm passing it to [team] to look at as an exception. They'll come back by [time].

Near-miss cases should reach someone with discretion rather than being declined automatically.

8. Well outside the window

This is [duration] past the returns period, so a refund isn't something we can do. What I can offer is [alternative], if that's any use.

Plain and final, with an alternative rather than an apology substituting for one.

9. Excluded category

[Category] items can't be returned once [condition], which is a hygiene requirement rather than our preference. I know that's frustrating.

Explaining the reason converts a substantial share of would-be complaints into accepted outcomes.

10. Condition requirements not met

The policy needs items unused and in original packaging, and from what you've described that isn't the case here. I can check whether [alternative] applies instead.

State the requirement rather than the judgement, so the decision reads as policy rather than opinion.

Alternatives and Partial Outcomes

Alternatives should be offered as options rather than as substitutes for a refund the customer is entitled to.

11. Exchange offered

I can refund this, or swap it for [alternative] which might solve the actual problem. Either is fine — which would you rather?

Offering both, with the refund named first, keeps this a genuine choice rather than a deflection.

12. Partial refund

Given [circumstance], I can refund [amount] and you keep the item. That's [proportion] of what you paid. Does that work, or would you rather return it for the full amount?

Naming both the amount and the proportion prevents the sense of an arbitrary figure.

When not to offer an alternative

A customer clearly entitled to a refund who is offered credit instead experiences it as obstruction, and it reliably produces escalation.

Alternatives belong where the entitlement is unclear or where the customer has expressed a preference.

Disputes and Escalation

Certain phrases in a refund conversation should end the automated or scripted handling immediately.

Chargeback language

Any mention of contacting the bank or disputing the charge should route to a person immediately, since the commercial calculation changes entirely at that point.

A chargeback costs considerably more than most refunds, which usually makes resolving it directly the better outcome.

Legal references

References to consumer rights, trading standards or legal action need someone familiar with the obligations, which frequently exceed the stated policy.

Applying policy rules to a statutory rights claim is a mistake with real exposure.

Repeated requests and high value

A pattern of refund requests, or an amount above the agreed threshold, warrants human review for both fraud and commercial reasons.

The thresholds should come from the documented policy rather than being decided in the moment.

Keeping Refund Answers Consistent

Refunds are where inconsistency costs most, since customers compare outcomes and perceive unfairness quickly.

Decisions documented centrally

Eligibility, thresholds and discretion limits should be written once and applied by everyone, since variation here reads as arbitrary treatment.

This is playbook work rather than training, and it produces consistency immediately rather than gradually.

Same answer across channels

A customer who gets a different outcome by phone than by chat will learn which channel to use, which distorts volume and undermines the policy.

Automated and human decisions should draw on the same rules for this reason.

Recording exceptions

Where discretion is exercised, recording it prevents the exception becoming an unwritten precedent nobody agreed to.

Reviewing exceptions periodically also identifies where the policy itself should change.

Handling Refunds in Chatboq

Chatboq applies eligibility from the documented policy, processes qualifying refunds in conversation and escalates the defined exception cases.

Eligibility checked automatically

Return window, category exclusions and condition requirements are checked against the actual order, so the position is stated accurately rather than approximately.

This removes the hedging that occurs when an agent is unsure whether a request qualifies.

One policy for both routes

Automated decisions use the same rules agents follow, so a customer receives the same outcome regardless of how they contacted.

Discretion thresholds are configured explicitly, which keeps exceptions deliberate rather than incidental.

Escalation before it becomes a dispute

Chargeback language, legal references, high-value requests and repeat patterns route to a person before any scripted response is given.

Catching these early is what keeps a refund conversation from becoming a formal complaint.

Recording the reason every time

Refund reasons aggregated by product identify quality and description problems that no other data source surfaces as directly.

Reporting these to merchandising and product teams turns a support cost into a source of improvement.

Frequently AskedQuestions

Document eligibility and discretion limits centrally, apply the same rules to automated and human decisions, and record exceptions so they do not become precedent.

On any mention of a chargeback or legal action, above the agreed value threshold, and on a pattern of repeated requests from the same customer.

Route to someone with discretion rather than declining automatically, since near-miss cases are where rigid policy produces avoidable complaints.

Only as a genuine choice alongside the refund. Offering it instead of an entitlement reads as obstruction and frequently produces a chargeback.

State the requirement rather than a judgement, explain the reason briefly, and offer whatever alternative exists. A bare refusal produces escalation almost every time.

Confirmation of the order, the eligibility position stated plainly, the decision with amount and timing, and an alternative where policy allows one.