# Consumer Resolution

> Resolve a consumer complaint, return, refund, cancellation, warranty, defective/missing order, subscription, chargeback, or seller/platform dispute with evidence and current jurisdiction-specific rules. Build the remedy ladder, deadlines, proof checklist, and copy-ready complaint or escalation; never submit without approval. Turkish triggers: iade alamıyorum, ayıplı ürün, garanti, sipariş gelmedi, abonelik iptali, satıcı reddetti, hakem heyeti/chargeback, şikâyet yaz.

- Skill: `yigityildiz0/consumer-resolution` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add yigityildiz0/consumer-resolution`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yigityildiz0/consumer-resolution/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: yigityildiz0 (https://skillmd.com/u/yigityildiz0)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/yigityildiz0/consumer-resolution

---


# Consumer Resolution

Turn a problem into an evidence-backed resolution path. Laws, deadlines,
exceptions, and forum rules vary by jurisdiction and date; verify the exact
transaction before asserting a right.

## Workflow

1. **Identify the transaction.** Resolve country/jurisdiction, consumer and
   seller locations, trader versus private seller, product/service/digital
   content, purchase channel, order and delivery dates, payment method, defect
   or requested cancellation, amount, and desired remedy. Ask one compact
   question only when a missing fact blocks the correct route.
2. **Preserve evidence.** Build a dated ledger of invoice/order, listing and
   advertised claims, terms at purchase, payment, delivery/tracking, photos or
   diagnostics, support messages, repair attempts, cancellation notices, and
   seller responses. Preserve originals and export disappearing chats/pages.
3. **Separate four layers.** Distinguish verified facts, seller/platform policy,
   statutory rights, and payment-network remedies. A store policy cannot be
   assumed to replace the law, and a chargeback is not the same as a legal claim.
4. **Research current authority.** Prefer official legislation/regulators,
   government consumer portals, court/tribunal rules, and official card/payment
   terms. Record effective date, jurisdiction, exceptions, limitation or filing
   deadlines, required pre-complaint steps, fees, and evidence standards.
5. **Choose the remedy ladder.** Start with the narrowest effective request,
   then seller formal notice, platform/payment dispute, regulator/ADR/tribunal,
   and professional legal help when value, complexity, urgency, or risk warrants
   it. Do not threaten remedies that are unavailable or unsupported.
6. **Draft precisely.** State identity, chronology, defect/breach, evidence,
   requested remedy, verified basis, reasonable deadline, and next escalation.
   Keep tone firm, factual, and non-defamatory.
7. **Protect external state.** Drafting and preparing forms is allowed. Do not
   send, submit, cancel, charge back, publish, or accept a settlement without
   explicit task-scoped approval and a final preview.
8. **Track outcome.** Record case/reference numbers, response deadlines,
   settlement terms, return shipping, refund completion, and the next trigger.

Use `message-writer` when a polished final email/chat is the main deliverable.
Use `legal-research` when the dispute turns on contested legal interpretation,
procedure, or material litigation risk.

## Output contract

```markdown
## Recommended next move
<one concrete action and deadline>

## Evidence and timeline
<verified chronology; missing proof clearly marked>

## Rights and routes
| Route | Current source | Deadline/condition | Evidence | Risk |
|---|---|---|---|---|

## Copy-ready draft
<factual request; no invented facts>

## Escalation if refused
<ordered steps, approval point, and uncertainty>
```

Label legal information and jurisdiction assumptions clearly. Do not promise a
refund, chargeback, award, or regulator outcome.