A chargeback notice can arrive weeks after a support conversation has ended. The customer may quote a sentence from a chat or a call and argue that the business broke its word. The support team then has to reconstruct what was said without rewriting history. A careful evidence note makes that reconstruction possible and keeps the response factual.
This guide is for support leads, dispute coordinators, and agents who may be asked to explain a promise during a chargeback. It covers how to capture the original wording, how to compare it with the refund policy, and how to hand a clean packet to the dispute team. The goal is not to win an argument. The goal is to show what happened and what the customer was owed.
Start with the customer's claim
Read the chargeback reason and the customer's statement before opening the support record. The customer may claim that an agent promised a full refund, a replacement, or a credit that never arrived. Write the claim in one sentence using the customer's own words. That sentence becomes the question the evidence note must answer.
Check whether the claim refers to a specific conversation or to a general impression. A customer who quotes a date and an agent name is easier to trace than one who says the team "always promises refunds." Record the channel, the date, and any reference number the customer supplied. If the customer attached screenshots, save them with the case rather than retyping them. Those details let a reviewer find the original message without asking the customer to resend it.
Do not label the claim as false at this stage. The support record may be incomplete, and a missing note is not proof that nothing was said. Treat the claim as a testable statement until the evidence is assembled. A neutral first read keeps the rest of the work honest.
Collect the promise record
Pull the original transcript, the call recording reference, and the case notes for the date in question. Quote the promise exactly, including the conditions around it. A sentence such as "we can refund the delivery fee once the carrier confirms the delay" means something different from "we will refund everything." The note should preserve that difference. Read the sentences before and after the quote so the condition is not lost.
Record who made the statement and in what role. An agent may have been following a script, improvising, or repeating a supervisor's instruction. The role matters because the dispute team needs to know whether the promise was authorized. Add the name of any supervisor who approved an exception.
Check the timestamps against the customer's account and the payment record. A promise made before a charge posted is different from one made after the customer had already disputed it. Put the times in a single time zone and say which one. The refund status answer guide shows how to keep those dates readable.
Match the promise to the charge
List the charge that is under dispute and the remedy the customer expected. The disputed amount may cover several items, so a general promise can look larger than the actual charge. Break the amount into its parts and mark which parts the promise covered. This step prevents an overbroad refund claim from going unchallenged.
Compare the promise with the policy that was in force on the date it was made. Policies change, and an old conversation may have been governed by an older version. Save the policy version and its effective date with the evidence packet. If the policy changed later, say so instead of applying the new rule backward.
Identify what the customer already received. A partial refund, a store credit, or a replacement may have reduced the remaining balance. Show each remedy with its date and reference number. The dispute team should be able to calculate the open amount without calling the support queue.
Explain the refund status
Describe the refund in the terms the payment system uses. A refund can be approved, submitted, settled, or rejected, and each state has a different meaning. Do not write "refunded" when the record only shows an approval. The customer's bank may still be processing the transaction.
State the destination and the expected posting window. A refund sent to an expired card may need a different path, and the customer should not be told to wait indefinitely. If the destination changed, record who authorized the change. The refund denial note guide explains how to name a review path without implying a result.
Separate the support promise from the bank's timeline. The business may have released the funds while the card issuer still shows a pending credit. Put both dates in the note so the dispute team can see where the delay sits. A clear timeline is more persuasive than a paragraph of apology.
Avoid a second promise
Do not answer the chargeback with a fresh assurance that the customer will be paid. The dispute process has its own rules, and a new promise can create another obligation. Write only what the record supports and what the business has approved. If a goodwill credit is still possible, route it through the normal approval path.
Tell the customer what the team has sent to the dispute reviewer without predicting the outcome. A short acknowledgment that the case is being reviewed is usually enough. Avoid language that sounds like a threat or a lecture. The customer already knows they filed a dispute.
Keep the tone consistent with the rest of the case history. If earlier messages were warm, a sudden legalistic reply will look defensive. If earlier messages were formal, sudden familiarity will look false. The evidence note should sound like the same team that handled the original contact.
Coordinate with the dispute team
Send the packet as one file with a short index at the top. Include the claim, the promise quote, the policy version, the transaction record, and the remedy history. Name a contact who can answer follow-up questions within one business day. A packet that ends with an unanswered phone number slows the review.
Ask the dispute team what format they need before assembling the file. Some teams want a single PDF, while others work from a case system with linked evidence. Follow the format that the reviewer will actually open. A perfect packet in the wrong format is still a delay.
Record the date the packet was sent and the date the reviewer acknowledged it. If the reviewer asks for more evidence, add it to the same case rather than starting a new thread. The case context standard offers a simple structure for keeping the record continuous. If the reviewer does not acknowledge the packet, follow up with the dispute owner rather than assuming it arrived.
Close with a dated record
Close the support side of the case only when the dispute team confirms it has what it needs. Add a note that names the disputed amount, the evidence sent, and the reviewer's response. If the dispute remains open, set a follow-up task with a date. Do not leave the customer waiting without a check-in.
Record the outcome when the dispute resolves, including whether the business won, lost, or settled. A loss is not automatically a support failure, but it may reveal a promise that should not have been made. Feed that finding into coaching and policy review. The same phrase should not create the same problem twice.
Review the note later for anything that reads as blame. The customer may have misunderstood, but the record should still be respectful. A dispute file can be read by people outside the support team, and the wording should hold up to that audience. A neutral description of the customer's request is safer than a summary that assigns motive.
A chargeback evidence note is a record of a promise and a payment, not a contest of memory. It should show the exact words, the governing policy, and the remedy already given. The reviewer can then decide the case on evidence rather than on volume. That is the most the support team can honestly provide.
