How should you reply to a customer who emails your support team while their chargeback is open?

Why that email is the best thing that has happened to your case

Most chargebacks arrive with no human attached. You get a reason code, a date, and maybe one line of customer description typed by a bank agent. That is why so many responses end up arguing with a ghost. When the same customer writes to your support address, you suddenly have the thing evidence packets almost never contain: the cardholder describing the purchase in their own words. Even a furious message usually confirms that they recognize your business, know what they bought, and remember roughly when it happened. That is identity, awareness, and product knowledge in a single paragraph you did not have to build. Related: Understanding Chargeback Reason Codes

It is also the only stretch of the process where the outcome still moves. Once your response is submitted, the file sits with the issuer for a stretch that typically runs several weeks and can run longer. A conversation right now can end with the customer calling their bank to withdraw, or at minimum with a clean record of you offering a reasonable remedy quickly. Speed matters more than polish here. Many of these emails exist because a renewal surprised someone, they tapped dispute in a banking app first, and then went looking for the merchant. Reply in hours, not days, while they are still in a fixing mood. Related: Meeting Dispute Deadlines

Keep reading: Why Most Chargebacks Are Lost, Building a Strong Evidence Packet, Understanding Chargeback Reason Codes. See how DisputeLoom helps you chargeback evidence packager for stripe sellers.

What to write, and the sentences that can cost you the case

Keep it short and structured: thank them for writing, restate the order facts plainly, name the specific remedy you can offer, and end with one question. Order facts means the date, what was bought, the amount, and how it was delivered. Nothing about card numbers, nothing about your dispute ratio, no wall of policy text. One question at the end matters because it keeps the thread alive and it usually produces a reply that pins down a useful detail, such as which email address they used or which family member placed the order.

Now the sentences to never put in writing. Do not mention collections. Do not suggest the customer will be banned, reported, or investigated. Do not imply that disputing is fraud, and do not phrase a refund as conditional on them dropping the case. Card networks and acquirers take a dim view of pressuring a cardholder, and a screenshot of that message can end up in the file the analyst reads. Also avoid promising that you will cancel the dispute. You cannot. Only the issuer can close it, and a promise you cannot keep turns a cooperative customer back into an angry one a week later.

Getting a withdrawal on the record without relying on it

If the customer agrees the charge was valid, ask for two specific things. First, that they contact their bank and say they want to withdraw the dispute, because you cannot do it for them. Second, that they reply to your email confirming they made the call, with the date and roughly who they spoke to. That reply is useful evidence even if nothing else comes of it, since it is the cardholder stating the transaction was authorized and the complaint resolved. Make the request easy: one sentence, no form, no attachment. Related: What Banks Look For in Evidence

Then keep working the case as though the withdrawal will not happen, because often it does not arrive in time or at all. Some issuers close a case on a cardholder withdrawal, many keep it running on the original schedule, and the deadline in your processor dashboard does not move because someone made a phone call. Assemble and submit the full response before that deadline regardless. If you decide instead to make the customer whole, do not refund the disputed charge: accept the dispute so the money moves once, and tell them their bank will return it. Related: How do you prove a subscriber actually used your software before disputing a renewal charge?

Turning the thread into evidence an analyst can read in a minute

Export the whole conversation as a clean document with headers intact: sender, recipient, subject, and the full date and time including timezone. Resist the urge to crop to the good part, because a trimmed thread looks curated and invites doubt about what was removed. Order it oldest message first so it reads as a timeline. If the useful admission sits three messages deep, add a one line pointer at the top of your written narrative that quotes the sentence and gives its date, so the analyst finds it without reading the whole exchange.

Then clean it. Redact partial card numbers, other customers' details, and any internal chat commentary your support tool merged into the thread. Export only the customer facing messages if your help desk keeps private notes alongside them. Finally, check that the timestamps agree with the rest of your packet. If your order record says one date and the email header says the day before, the mismatch is almost always a timezone setting, but an analyst reading quickly may just call it inconsistent. Line the two up, or explain the offset in a single sentence.