Billing Error Dispute Dossier

Purpose

Turn a confusing billing problem into a structured, evidence-backed dossier the user can copy into email, chat, support forms, card-provider disputes, or personal records. Focus on factual organization, clean escalation, and accurate documentation rather than pressure tactics.

This is a prompt-only consumer documentation workflow. It is not legal, tax, accounting, banking, or financial advice.

Use This Skill When

Use this skill when the user reports any of these situations:

• An incorrect, duplicate, unauthorized, or unexpected charge.
• A subscription billed after cancellation or trial expiration confusion.
• A promised refund that has not arrived.
• A service not delivered, partially delivered, or billed at the wrong rate.
• A hidden fee, contract mismatch, invoice error, or merchant support deadlock.
• A need to organize evidence before contacting a merchant, bank, payment app, card issuer, platform, or marketplace.

Do not use it to fabricate claims, evade legitimate charges, abuse chargebacks, threaten unsupported legal action, or dispute accurate transactions.

Best Inputs

Ask for only what is needed. If details are missing, proceed with placeholders and a short follow-up question list.

• Merchant, platform, or biller name.
• Amount, currency, billing date, and payment method.
• What the user believes is wrong and the correction they want.
• Purchase date, cancellation date, refund request date, or service date if relevant.
• Evidence already available: receipt, invoice, terms, cancellation confirmation, screenshots, support emails, chat transcript, delivery logs, bank record, or account page.
• Prior contact attempts: date, channel, agent name if known, ticket number, and outcome.
• Deadline or urgency, such as a card dispute deadline, bill due date, or service shutoff risk.

Workflow

1. Record the charge facts. Capture merchant, amount, date, payment method, account or order identifier, and the exact issue being disputed.
2. Build the timeline. List purchase, billing, discovery, cancellation, refund request, support contact, promised resolution, and follow-up dates in order.
3. Classify the dispute. Label the issue as duplicate charge, unauthorized charge, subscription cancellation, service not delivered, refund delay, hidden fee, pricing mismatch, contract mismatch, invoice error, or other.
4. Map the evidence. Match each claim to evidence the user has, evidence still needed, and where it can be found.
5. Write the claim summary. Draft a concise factual summary that states what happened, why the charge appears wrong, what evidence supports the claim, and what remedy is requested.
6. Draft the first-contact message. Prepare a polite merchant-support message for email, chat, or ticket forms with a clear remedy request and evidence list.
7. Prepare escalation materials. If merchant resolution fails, create a bank, card issuer, payment app, marketplace, or platform escalation summary that avoids unsupported legal language and follows provider-specific rules when supplied by the user.
8. Create the tracking plan. Produce a contact log, follow-up schedule, deadline reminders, and next-step decision points.

Output Format

Return the dossier in this order:

1. Dispute Snapshot

2. Timeline

3. Evidence Checklist

4. Claim Summary

A short paragraph suitable for a support case or payment-provider dispute form.

5. Merchant Message Template

A copy-ready message with subject line, concise facts, requested remedy, attachments, and requested response date.

6. Escalation Summary

A separate copy-ready summary for a card issuer, bank, payment app, marketplace, or platform if escalation is appropriate.

7. Contact Log and Follow-Up Schedule

8. Open Questions

A short list of missing facts that would strengthen the dossier.

Message Style

• Be factual, calm, and specific.
• Ask for a concrete remedy: refund, correction, reversal, credit, cancellation confirmation, itemized bill, or written explanation.
• Include dates, amounts, order identifiers, and evidence names.
• Avoid insults, accusations, unsupported threats, or emotional pressure.
• Use placeholders for sensitive details instead of requesting full account numbers.

Safety Boundary

• Do not provide legal, tax, accounting, banking, or financial advice.
• Do not instruct fraud, chargeback abuse, false claims, document falsification, or evasion of legitimate charges.
• Do not guarantee refunds, reversals, dispute outcomes, or timelines.
• Do not override merchant, bank, card-network, marketplace, payment-app, or regulator instructions supplied by the user.
• Encourage the user to follow official dispute procedures and deadlines for their provider.
• Minimize sensitive data. Use partial account numbers, order identifiers, and redacted documents where possible. Never ask for passwords, full card numbers, full bank numbers, full SSNs, one-time codes, or account credentials.
• For large losses, repeated fraud, identity theft, debt collection, service shutoff, or court/legal threats, recommend appropriate professional, provider, regulator, or law-enforcement guidance.

Example Prompts

• "I was charged twice for the same subscription. Help me organize a dispute."
• "A hotel added a fee that was not in my booking confirmation. Draft the evidence packet."
• "I cancelled a trial before the deadline but still got billed. What should I send support?"
• "My refund was approved three weeks ago but never arrived. Build a follow-up dossier."
• "The app store rejected my refund request. Help me prepare an escalation summary."