Warranty Return Dispute Kit

Overview

Helps users organize a product warranty, return, or defect dispute into a factual packet they can use with a seller, manufacturer, marketplace, or payment provider. The skill focuses on documentation, timelines, calm communication, and follow-up tracking.

This skill is not legal advice and does not interpret laws, threaten parties, fabricate evidence, or guarantee refunds, replacements, chargebacks, or warranty outcomes. It helps the user communicate from their own records and the seller's or manufacturer's documented policies.

When to Use

Use this skill when the user asks to:

• dispute a denied warranty claim
• organize evidence for a defective product return
• respond to a seller who rejected a return
• prepare a warranty escalation message
• track support contacts and next deadlines
• summarize a product issue for customer support

Trigger keywords: warranty dispute, return dispute, denied warranty claim, defective product, product return evidence, warranty escalation, refund request denied, seller dispute, manufacturer warranty claim, customer support escalation

Required Inputs

Ask for factual, non-sensitive details:

• Product: Item name, model, serial number if needed, purchase date, order date, delivery date, seller, marketplace, and manufacturer.
• Policy: Return window, warranty term, claim requirements, exclusion language, and any support reference numbers the user already has.
• Problem: What failed, when it started, how it affects use, and whether the issue is repeatable.
• Evidence: Receipt or invoice, order confirmation, warranty page, photos or videos, packaging photos, troubleshooting steps, chat transcripts, emails, repair notes, shipping records, and denial message.
• Timeline: Purchase, delivery, first use, first issue, support contacts, claim submission, denial, and upcoming deadlines.
• Desired resolution: Repair, replacement, refund, store credit, missing part, return label, or written explanation.

Do not request passwords, full payment card numbers, government IDs, private account credentials, or unnecessary personal data. Use placeholders for account, order, or claim numbers when drafting messages.

Workflow

Step 1: Capture Product, Seller, Dates, and Issue

Create a case summary:

If dates are missing, mark them as gaps instead of guessing.

Step 2: Build the Evidence Packet Checklist

Group the evidence by purpose:

• Proof of purchase: Receipt, invoice, order confirmation, payment confirmation with sensitive data redacted.
• Policy proof: Warranty page, return policy, product listing claims, seller messages, manufacturer support terms.
• Defect proof: Photos, videos, error messages, failed function description, comparison to expected operation.
• Care and use proof: Setup steps, troubleshooting steps, maintenance records, normal-use explanation, product manual references.
• Communication proof: Emails, chat transcripts, call notes, support ticket numbers, denial message, prior promises.
• Logistics proof: Delivery confirmation, tracking, return-label status, packaging photos, inspection or repair report.

Only use evidence the user actually has. Do not invent dates, statements, defects, receipts, photos, policy language, or support promises.

Step 3: Build the Event Timeline

Produce a chronological timeline:

Flag missing facts that matter, such as unclear delivery date, no copy of warranty terms, missing denial reason, or no written support record.

Step 4: Draft Factual Support and Escalation Messages

Create concise messages the user can adapt. Keep tone calm, specific, and documented.

Initial or follow-up message structure:

1. Identify product, order, and claim reference using placeholders.
2. State the defect or return issue in one or two factual sentences.
3. Reference the purchase date, delivery date, warranty/return term, and prior support contact.
4. List attached evidence.
5. Ask for the specific resolution or a written explanation of the denial.
6. Request the next step and response timeframe.

Do not include threats, insults, fabricated leverage, false deadlines, or claims that cannot be supported. If the user wants to mention consumer rights, tell them to verify current rules with an official source or qualified professional first.

Step 5: Create Follow-Up Log and Deadline Tracker

Provide a log:

Provide a deadline tracker:

When deadlines are unknown, mark "verify" rather than guessing.

Output Format

Deliver:

1. Case summary
2. Evidence packet checklist
3. Event timeline
4. Missing facts and next evidence to gather
5. Factual support or escalation message
6. Contact log
7. Deadline tracker
8. Safety and scope notes

Safety & Compliance

• No legal advice, legal strategy, rights interpretation, or outcome prediction.
• No fabricated evidence, fake receipts, altered timelines, false statements, or invented support promises.
• No threats, harassment, intimidation, or false escalation claims.
• No refund, replacement, warranty, chargeback, or dispute outcome guarantees.
• Base all communication on user-supplied records, documented policies, and verifiable facts.
• Do not ask for or store credentials, passwords, full card numbers, government IDs, or unnecessary personal data.
• No executable code, APIs, network calls, or external account access.

Acceptance Criteria

1. Produces a factual case summary using only user-supplied details.
2. Creates an evidence packet checklist covering purchase, policy, defect, communication, and logistics records.
3. Builds a chronological timeline and marks missing facts without guessing.
4. Drafts calm support or escalation communication without threats, legal advice, fabricated claims, or guarantees.
5. Includes a contact log and next-deadline tracker.
6. Stays prompt-only with no executable code, APIs, network calls, credentials, or external actions.