The prompt
Score 10 of 10, Excellent
Use it when A customer disputed a card payment with their bank, and you need a clear rebuttal letter that matches the dispute reason and points to your evidence.
- {{business}}
- {{dispute_details}}
- {{what_happened}}
- {{evidence}}
- {{policy}}
Full prompt and why it works
Prompt
Write a chargeback response letter for {{business}} about the disputed payment below, so that the card issuer's dispute reviewer can match our evidence to the dispute reason quickly. Reviewers read many of these, so the letter should answer the stated reason, set out the facts in order, and point to each piece of evidence by name. Dispute details from the payment processor (reason code and description, amount, transaction date, response deadline): """ {{dispute_details}} """ What happened (the order, delivery or service, contact with the customer, any refund requests): """ {{what_happened}} """ Evidence I can attach, with file names: {{evidence}} Our terms or refund policy, and how the customer agreed to them: {{policy}} Write: 1. The letter, under 450 words, with these parts: Summary (two sentences on why the charge is valid, tied to the dispute reason), Transaction details (date, amount, order number and what was bought), Timeline with dates, Response to the dispute reason, Evidence list (numbered, matching the file names), Request (that the chargeback be reversed). 2. A checklist for me: the response deadline, and evidence that would help with this kind of dispute reason but that I have not listed, written as questions. 3. A note to me if the facts suggest that accepting the dispute or refunding would be wiser, with the reason, for example if the customer asked for a refund we never answered. Rules: - Use only the facts and evidence above. Do not invent tracking numbers, signatures, dates, messages or policy wording. - Describe each file only from what I have told you about it, since you cannot see the files. - Make sure every statement in the Response section points to a numbered item in the evidence list. - Stay factual and polite about the customer. Do not accuse them of fraud unless my facts include evidence of it. - Do not quote card network rules or regulations from memory, because they change and differ by network; in the checklist, ask me to check the processor's requirements. If the dispute reason is unclear, or my evidence does not address it, say so at the top of the checklist rather than writing around the gap.
Variables
- {{business}}
- Your business name.
- {{dispute_details}}
- The dispute notice from your processor: reason code and wording, amount, dates and deadline.
- {{what_happened}}
- The facts of the sale and what happened after, with dates. Leave out full card numbers.
- {{evidence}}
- Files you can attach, with names and what each shows, for example "1-invoice.pdf; 2-tracking.png, delivered May 3; 3-emails.pdf".
- {{policy}}
- Your refund or cancellation terms and how the customer saw or accepted them, for example "checkbox at checkout".
Why it works
- Format. Fixed parts with a numbered evidence list that matches your file names let a busy reviewer tie every claim to an attachment.
- What to avoid. No remembered card network rules, no fraud accusations, and no guesses about what a file contains, the mistakes that most often weaken a response.
- If unsure. If your evidence does not answer the dispute reason, you are told before you submit, along with a note when refunding would be the wiser move.