The customer's own messages from before the dispute win more chargebacks than your terms of service. Here is how to find them and use them.
When a chargeback comes in, most merchants grab the same things: the terms of service, the refund policy, the order confirmation and a screenshot of checkout.
The bank doesn't give those much weight. They're documents a business wrote about itself.
The evidence that wins more cases is usually somewhere else. It's in your support inbox, it was written by the customer, and it almost never makes it into the reply.
Why the customer's own words win
A chargeback is decided by a reviewer at the customer's bank. They work through a form for the dispute reason on the notice, and they spend about 90 seconds on your file.
The customer has already told the bank a story:
- "The parcel never came."
- "It wasn't what I ordered."
- "I cancelled and you still charged me."
- "I never made this purchase."
Your job is to show the story doesn't match what happened. Nothing does that better than what the customer wrote to you before they went to the bank. They wrote it when they had no reason to bend the truth.
What it looks like for each type of dispute
"The parcel never came." Tracking only shows a parcel reached an address. It doesn't show who lives there. These messages are much stronger:
- An email two days later asking how to use the product. They had it.
- A message the day before delivery asking where the order was. They were expecting it at that address.
- A chat saying the box was left with a neighbour. That usually settles it.
"It wasn't what I ordered." Customers often write to support first. What they asked tells the bank what they really expected. If they asked to swap it for a different colour, it's a return, not a product that was described wrongly.
"I cancelled and you still charged me." Either they contacted you to cancel or they didn't. An inbox with no cancellation request before the charge, plus a message afterwards asking about a new feature, answers this better than your cancellation policy ever will.
"I never made this purchase." If the same customer emailed you about delivery of that exact order, they've answered the fraud claim for you.
It also shows how you behaved
Some banks give extra weight to the conversation between you and the customer.
- A thread where you replied and offered a fix shows you dealt with the problem.
- A thread with no reply gives the bank nothing on your side.
- A refund offer the customer turned down before going to the bank is persuasive. It shows they had a way to get their money back and chose the bank instead.
Why this evidence never reaches the bank
It's rarely a strategy problem. It's a filing problem.
- Support lives in one tool, orders in another, and disputes arrive as an email to the finance inbox.
- The person answering the dispute often can't see the support history, or doesn't think to look.
- Many help-desk and chat tools archive or delete old conversations after a set period.
- Messages sent to someone's personal email are invisible to everyone else.
By the time anyone looks, the one line that would have won the case is gone, or buried in a thread of 40 messages.
How to fix it (no new software needed)
- Make every support conversation searchable by the customer's email address and order number.
- Search the inbox every time a dispute arrives, before writing anything.
- Keep conversations for as long as a customer could still dispute the charge. That can be many months after the order.
- Forward messages that arrive elsewhere (social media, personal email) into the help desk so they sit with the customer's record.
How to use it in the letter
Don't send the whole thread. Reviewers won't read it, and the important line gets lost.
Instead:
- Quote the one or two lines that matter.
- Add the date and where it came from (email, chat, phone note).
- Label what it proves. For example, "Customer confirms the parcel arrived" or "Customer asks for help using the product after delivery."
- Put the quote near the top, next to the records it supports.
- Attach the full thread at the back for anyone who wants it.
Pick the right lines
Not every message helps. A line that wins a "never arrived" case can hurt you in a "not as described" case, because the same customer's complaint becomes evidence for them.
An expert reading the thread picks the lines that answer the dispute reason on the notice. They leave out anything that gives the bank a reason to side with the customer. Usually that's two or three sentences, not twenty.
The inbox can stop disputes too
A customer who gets a quick, clear answer about a late parcel, a confusing charge or a cancellation has less reason to go to their bank.
If your support team can spot a customer heading towards a dispute and offer a refund or a fix first, you save the fee, the time and the hit to your chargeback ratio.
Where we come in
representments.com writes chargeback replies that use this evidence properly.
- Forward the chargeback email, plus any messages from the customer.
- Within 48 hours you get a letter written by industry experts for that dispute reason and the customer's bank.
- Every piece of evidence is labelled for the reviewer.
- You file it through your own payment company.
Start with a free first letter.
Sources
- Tracking shows delivery to an address but not who lives there; a customer message asking when the order would arrive, sent before the carrier marked it delivered, undercuts a later claim that no order was expected.representments.com, Visa 13.1: customer says the package never arrived (/learn/customer-claims-didnt-receive-package)
- Some issuing banks weigh the merchant's communication trail with the customer more heavily than the card-network average.representments.com, Why the customer's bank matters as much as the dispute reason (/learn/issuer-decides-as-much-as-reason-code)
- Padding a reply with terms-of-service quotes and generic policies tells the bank the case is weak.representments.com, Should you refund or fight this chargeback? (/learn/should-i-refund-or-fight-this-chargeback)
- Bank reviewers spend about 90 seconds per dispute file, working from a structured form for the dispute reason.representments.com, How a bank reviewer reads your reply (/learn/ninety-second-analyst-read)
- Long email threads with the relevant line buried give the reviewer more to read and nothing to tick; the line that matters belongs at the top.representments.com, How to write a chargeback rebuttal letter (/learn/first-letter-structure)