KoltrixRefund and billing emails: templates and judgment calls
Copyable reply templates for duplicate charges, forgotten cancellations, partial refunds and failed payments, plus guidelines on when to refund without debate.
On this page(10 sections)
Billing emails are where customers are most anxious and support teams are most likely to sound like a legal department. Money makes people nervous on both sides of the conversation.
The fix is to decide your judgment calls ahead of time, so the person replying isn't inventing policy under pressure, and to have templates that sound human. This post gives you both: four templates for the most common billing emails, and a set of guidelines for when to refund, when to escalate, and how to record what you decided.
First, decide who can approve what
Templates are useless if the person replying doesn't know whether they're allowed to say yes. Write down approval levels before anything else. A small SaaS team might use something like this:
| Situation | Who can approve | Notes |
|---|---|---|
| Clear error on our side (duplicate charge, wrong plan) | Anyone in support | Refund immediately, no debate |
| Forgot to cancel, renewal within a few days | Anyone in support | Full refund of the latest renewal |
| Forgot to cancel, renewal weeks ago with usage | Support lead | Partial refund or credit |
| Request outside policy (unhappy after months of use) | Support lead or founder | Case by case |
| Annual plan, mid-term cancellation | Founder or finance | Depends on your terms |
| Any refund above a set amount | Founder or finance | Pick a threshold that fits your prices |
The exact thresholds depend on your prices and margins. What matters is that they exist, and that frontline staff can resolve the most common cases without waiting for anyone.
Template 1: Duplicate charge
This is your mistake, or your payment processor's. Don't make the customer prove anything.
Subject: Re: Charged twice this month
Hi [Name],
You're right, you were charged twice on [date]: once at [time] and
again a few minutes later. That second charge shouldn't have
happened.
I've refunded the duplicate charge of [amount] just now. Depending on
your bank, it usually shows up within a few business days. You don't
need to do anything else.
Sorry for the hassle. If it doesn't appear by [date], reply here and
I'll chase it with our payment provider.
[Your name]
Note the specifics: date, amount, when to expect it, and what to do if it doesn't arrive.
Template 2: Forgot to cancel
The single most common refund request in subscription businesses. People forget. Being generous here builds goodwill that often brings customers back later.
Subject: Re: Didn't mean to renew
Hi [Name],
No problem, this happens a lot. I've cancelled your subscription so
you won't be charged again, and I've refunded the [amount] renewal
from [date].
Your account stays accessible until [date] in case you want to export
anything. After that, [what happens to their data, per your policy].
If you ever want to come back, your account can be reactivated from
the billing page.
[Your name]
Avoid asking "Why are you leaving?" in the same email as the refund. If you want feedback, ask in a separate, optional follow-up.
Template 3: Partial refund or credit
For cases where a full refund isn't appropriate but some recognition is: weeks past renewal, part of the period used, or a service problem that affected them for a few days.
Subject: Re: Refund request
Hi [Name],
Thanks for explaining what happened. I've looked at your account: the
renewal went through on [date] and the account has been used since,
so a full refund isn't something we'd normally do here.
What I can do is refund [amount], which covers the unused part of
this billing period, and cancel the subscription so nothing renews.
[Or: add a credit of [amount] to your next invoice.]
If that works for you, I'll process it today. If there's something
I've missed about your situation, tell me and I'll take another look.
[Your name]
The last line matters. It signals that this is a decision made by a person, not a wall.
Template 4: Failed payment confusion
Customers often email after receiving an automated "payment failed" message, worried their account is about to vanish.
Subject: Re: Payment failed?
Hi [Name],
Nothing is lost. Your payment on [date] didn't go through, which
usually means the card expired or the bank declined it as a
precaution.
To fix it, update your card on the billing page: [link]. We'll retry
automatically once it's updated. Your account stays fully active
until [date], so there's no rush today.
If your card is fine and it still fails, reply here and I'll look at
the decline reason with you.
[Your name]
Reassurance first, then the action, then the deadline.
Judgment guidelines
Templates cover the routine. These guidelines cover the rest.
Refund without debate when:
- The error is clearly yours (duplicate charge, wrong amount, charge after cancellation)
- The amount is small relative to the cost of the conversation
- The customer barely used the product in the charged period
Slow down and escalate when:
- The request is large, or for a long period of past usage
- The customer mentions a chargeback or dispute (follow your payment provider's guidance)
- There are signs of fraud: several cards, mismatched details, requests to refund to a different card
- The customer is asking for something your terms explicitly rule out, and you're inclined to say yes
Never:
- Promise a refund before checking the account
- Refund to a different payment method than the original without finance approval
- Share billing details with anyone other than the account owner or billing contact
Tone rules for every billing email
Templates only get you halfway. The wording around them matters just as much, because billing conversations are where customers decide whether they trust you.
Lead with the outcome. If you're refunding, say so in the first two lines. If you're not, say that early too. Customers skim billing emails looking for the answer; don't make them hunt for it under three paragraphs of context.
Use numbers, not adjectives. "A refund of the full renewal amount, which you should see within a few business days" is better than "a prompt and generous refund." Specific dates and amounts remove anxiety.
Explain policy in plain words. "We don't refund months that have been used" reads as a rule. "Because the account has been active since the renewal, we'd normally offer a credit rather than a refund" reads as reasoning. The second is easier to accept, even when the answer is the same.
Never blame the customer. "You forgot to cancel" is technically true and lands badly. "This happens a lot" makes the same point without the sting.
Skip the upsell. A refund email is not the moment to suggest a cheaper plan, unless the customer asked about one. If downgrading might genuinely solve their problem, mention it once, briefly, as an option rather than a pitch.
Keep it short. Most billing replies need four to eight lines. Long explanations make people suspect there's a catch.
Handling the follow-up questions
Billing threads often get a second message. Prepare for the common ones:
- "When will I see it?" Give the processing time you actually observe, and say what to do if it doesn't appear.
- "Can you refund the previous months too?" Treat this as a new request and apply the approval table, rather than answering on the spot.
- "I need an invoice for this." Send a corrected invoice or credit note if your billing system supports it, and confirm the company details first.
Document every decision
Each refund or refusal should leave a trace. A short note in the thread or your billing system covers it:
Refund: [amount], reason: forgot to cancel, renewed 3 days ago,
approved by: [name], date: [date]
This helps when the same customer writes again, when finance reconciles, and when you review whether your policy is too strict or too loose.
Key takeaways
- Set approval levels in advance so frontline staff can resolve common cases immediately.
- Duplicate charges and recent forgotten renewals: refund quickly and kindly.
- Partial refunds and credits are a good middle ground; explain the reasoning and leave the door open.
- Failed-payment emails need reassurance before instructions.
- Escalate large, disputed or suspicious requests, and record every decision.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
