How to handle refund requests in Help Scout

A refund request is often the last step before a chargeback. A customer who asks for their money back and gets a slow or unclear answer may go to their bank instead, and then you lose the payment, pay a dispute fee, and spend time on evidence. A customer who gets a quick, clear answer usually does not.

This guide sets out a refund process for teams that support customers in Help Scout: how to recognise refund requests, decide quickly, issue the refund without leaving the conversation if you bill with Stripe, and keep a record that will help if a dispute comes anyway. Help Scout details come from its documentation: the Stripe app, saved replies, tags, workflows and custom fields. Refund and dispute rules come from Stripe’s refunds, how disputes work and dispute categories pages (all accessed November 2026).

Refund or dispute: why timing matters

Stripe’s documentation makes the stakes clear:

• Once a formal dispute is open, you cannot refund the payment outside the dispute process (how disputes work). You either accept the dispute or challenge it.
• At the inquiry stage, before a formal chargeback, a full refund can close the case without a dispute fee; Stripe notes that inquiries on partially refunded charges can still escalate.
• If the customer disputes while a refund is pending, Stripe recommends accepting or challenging the dispute rather than refunding again, to avoid paying twice.

The practical lesson: the cheapest refund is the one you issue before the customer calls their bank. A refund request sitting unanswered for three days is a chargeback risk.

Step 1: recognise refund requests fast

Create an automatic workflow in Help Scout (automatic workflows) with conditions on the subject or body containing words such as “refund”, “money back”, “charged twice”, “didn’t authorise”, “unauthorized charge” and “chargeback”. Actions:

1. Add the tag refund-request (tags).
2. Assign to whoever can approve refunds.

Watch for two phrases in particular: “I didn’t authorise this” and “I’ll contact my bank”. The first may be fraud or a family member using the card; the second means a dispute is close. Both deserve an answer the same day.

Step 2: decide with a simple policy

Agents should not have to ask a manager for every refund. Write down a policy that covers most cases and that matches what your terms say:

Situation	Typical decision
Charged after a cancellation request you missed	Refund in full, apologise
Renewal the customer forgot about, no use since	Refund or partial refund, per your policy
Duplicate charge	Refund the duplicate
“I didn’t authorise this”	Check the account; if it looks like fraud, refund and secure the account
Partial use, wants full refund	Per your policy; explain clearly either way
Long-term active user asking after months of use	Usually decline, politely, with the reason

Two things to keep in mind:

• Your refund policy only helps if the customer saw it. In a dispute, Stripe’s evidence fields include the refund policy and how it was disclosed to the customer before purchase (dispute categories).
• A refusal should be a reason, not silence. If you decline, say why, refer to the terms, and offer what you can (cancelling future renewals, a credit). A clear “no” with a reason is better evidence than no answer.

Step 3: issue the refund from the conversation

If you bill with Stripe, Help Scout’s Stripe app shows the customer’s subscriptions and invoices in the sidebar and lets agents issue full or partial refunds without leaving the conversation. Per Help Scout:

• It is installed under Settings > Apps > Stripe, and you choose which inboxes show it.
• The person installing it needs admin-level permissions or above in Stripe.
• Every Help Scout user with access to those inboxes can issue refunds from the sidebar, regardless of their own Stripe permissions.

That last point matters. Only show the app in inboxes handled by people who are allowed to refund, or put refund requests in a dedicated inbox.

If you bill elsewhere, agents refund in your billing system and confirm in the conversation.

Step 4: confirm in writing

Use saved replies so every refund gets a clear confirmation:

I’ve refunded [amount] to the card you paid with. Depending on your bank, it can take a few business days to appear. Your subscription is [cancelled / still active until (date)]. If anything still looks wrong on your statement, reply here and I’ll sort it out.

And for a refusal:

I’ve looked at your account. The charge on [date] is for [plan], which you’ve used since [date], so under our terms ([link]) it isn’t refundable. I’ve cancelled future renewals so you won’t be charged again. If I’ve missed something, reply here and I’ll look again.

Fill the brackets for each case. Never say a refund was issued before it actually was.

Step 5: record the outcome

Add a custom field (Plus and Pro plans) or tags for the outcome: refund-full, refund-partial, refund-declined. With the request tag from step 1, you can see:

• how many refund requests you get, and from which reasons;
• how long they take to answer;
• which declined requests later turned into disputes.

That last list is the one to study. If declined requests often become disputes you lose, your policy or the way it is explained needs work.

Common mistakes

• Answering the refund request with a retention offer. If the customer asked for their money back, a discount on next month does not answer the question. Answer it first; mention an alternative after, if at all.
• Partial refunds as a default compromise. On Stripe, inquiries on partially refunded charges can still escalate. If you refund to avoid a dispute, consider whether a full refund is the safer choice.
• Refunding without cancelling. If the customer wants out, a refund without a cancellation means another charge next month, and a dispute that time.
• Different answers from different agents. A written policy and saved replies keep decisions consistent, which matters when a reviewer reads your reply next to your terms.
• Letting “I’ll contact my bank” wait. That message deserves the fastest answer in your queue.

When a dispute comes anyway

Some customers will dispute regardless. When that happens, the conversation you just had is your evidence: the dated request, your reply, the refund or the reasoned refusal. Our guide to using Help Scout conversations as chargeback evidence explains how to extract and present it. Stripe’s early fraud warnings are a separate signal worth watching, since a proactive refund can sometimes prevent a fraud dispute.

Doing this with NoChurn

NoChurn’s Help Scout connector is read-only: it reads conversations and does not issue refunds, tag or reply in Help Scout. Conversations are matched to your customers by email; doubtful matches are suggested for you to confirm and never merged automatically. If a dispute opens on Stripe or Braintree, NoChurn gathers the evidence (cancel flow answers, emails sent, usage, and the matched refund conversation quoted verbatim with dates), drafts a response with AI and submits it only after you review it. Refund decisions stay with you, in Stripe or your billing system. See NoChurn + Help Scout.