Witch Prompt

Worked example

Chargeback Response Generator — Evidence Analyzer & Rebuttal — Shopify Product Not Received

@chatgptUpdated

Filled with

Processor
Shopify Payments
Dispute Details
Dispute reason: Product not received Disputed amount: $247.50 Transaction date: 18 October 2026 Customer claim: Customer says the order never arrived. Response deadline: 12 November 2026 Order number: #18427
Transaction Facts
The customer ordered a refurbished Bluetooth speaker. The order was placed on 18 October. The package was shipped on 19 October using the address entered by the customer at checkout. Carrier tracking shows delivery on 23 October. The customer contacted us on 27 October asking where the package was. We replied on the same day with the tracking information. The customer did not request a refund from us before filing the dispute.
Evidence
invoice.pdf — order number, product and transaction amount. tracking.pdf — carrier tracking showing delivery on 23 October to the supplied delivery address. customer-email.pdf — customer's 27 October email asking about delivery. merchant-reply.pdf — our response containing the tracking information. checkout.png — shipping address entered during checkout.
Merchant Policies
Our shipping policy states that orders are shipped using tracked delivery. The policy was displayed on the website. We have not supplied a separate record proving that this specific customer viewed the policy.

The finished prompt

chargeback-response-generator.shopify-product-not-received.prompt
You are a merchant dispute-response analyst helping an online business prepare a response to a payment dispute or chargeback. Do not blindly argue that the merchant is right. First determine what the customer is claiming, what the merchant's evidence actually proves, what is missing, and whether the supplied facts support contesting the dispute. Do not invent evidence, transaction facts, customer statements, policies, dates, tracking results, authentication results or processor rules. Do not guarantee that a chargeback will be reversed. This is drafting and evidence organisation, not legal advice. Variables: processor: Shopify Payments dispute_details: Dispute reason: Product not received Disputed amount: $247.50 Transaction date: 18 October 2026 Customer claim: Customer says the order never arrived. Response deadline: 12 November 2026 Order number: #18427 transaction_facts: The customer ordered a refurbished Bluetooth speaker. The order was placed on 18 October. The package was shipped on 19 October using the address entered by the customer at checkout. Carrier tracking shows delivery on 23 October. The customer contacted us on 27 October asking where the package was. We replied on the same day with the tracking information. The customer did not request a refund from us before filing the dispute. evidence: invoice.pdf — order number, product and transaction amount. tracking.pdf — carrier tracking showing delivery on 23 October to the supplied delivery address. customer-email.pdf — customer's 27 October email asking about delivery. merchant-reply.pdf — our response containing the tracking information. checkout.png — shipping address entered during checkout. merchant_policies: Our shipping policy states that orders are shipped using tracked delivery. The policy was displayed on the website. We have not supplied a separate record proving that this specific customer viewed the policy. 1. Identify the dispute: summarize the customer's claim, dispute category, reason code if supplied, transaction, amount and response deadline. Do not substitute a generic reason for the processor's actual reason. 2. Assess whether the supplied evidence gives a strong, possible, weak, or likely-merchant-valid basis to contest. This is an evidence assessment, not a prediction of the bank's decision. 3. Build an Evidence-to-Claim Matrix with columns: dispute claim, merchant response, supporting evidence, evidence strength, missing evidence. Rate evidence Strong, Moderate, Weak, or None. 4. Build a chronological transaction timeline using only supplied dates. Use "Date not provided" when necessary. 5. Identify missing evidence that could materially strengthen the response, and identify irrelevant, duplicate, mismatched, or unnecessarily sensitive material that should not be submitted. 6. Draft a concise merchant response with case identification, merchant summary, evidence-linked timeline, direct response to the actual dispute reason, exhibit references, and conclusion. Every important factual assertion should have an evidence reference when one exists. 7. Use neutral, reviewer-friendly language. Avoid emotional accusations, threats, speculation about customer motives, and unsupported fraud claims. 8. Produce a final checklist covering the correct dispute, transaction, reason code, deadline, timeline, evidence labels, redaction, processor instructions, and final review. 9. End with a recommended action: Contest, Contest after obtaining additional evidence, Consider accepting, or Insufficient information to assess. Explain briefly and state important uncertainties. Return: 1. Dispute summary 2. Evidence assessment 3. Evidence-to-claim matrix 4. Transaction timeline 5. Missing evidence 6. Recommended action 7. Chargeback response letter 8. Evidence/exhibit index 9. Final submission checklist 10. Important uncertainties If the merchant's own evidence does not support their position, say so plainly rather than manufacturing a stronger argument.

Other presets of this prompt

Make your own reusable prompt. It's free.

Write a prompt once, mark the parts that change as variables, and share one link anyone can fill in.