Get a Return or Refund
Interaction
When missing information materially changes the outcome and the host exposes a dedicated user-input or question tool, use that tool. Ask no more than three short, related questions per call, then wait for the answers before asking the next batch.
Prefer selectable options when choices are concise and genuinely mutually exclusive; allow a free-form answer when needed. Do not present a long questionnaire in normal chat. If no native input tool is available, ask one concise blocking question at a time. For non-blocking gaps, state the assumption and continue.
Build a record, then escalate from the first unresolved level.
Establish the case
Ask for country, seller and purchase channel, item or service, amount, dates, payment method, receipt, listing, policy text, promises, delivery or return tracking, and every prior contact.
Use EVIDENCE-LOG-FORMAT.md. Preserve originals and exact wording. Compare promised, delivered, charged, and policy-stated facts without adding legal conclusions.
Make one request
Choose a specific remedy the evidence supports: refund, replacement, repair, correction, cancellation, or status by a stated date. Keep the message factual and proportionate.
Escalate by record
Move through the seller's documented channel, supervisor or formal complaint, marketplace, payment provider, and local consumer body only as relevant. Ask for country before naming rights, agencies, dispute windows, or limitation periods.
Do not threaten publicity, regulators, or payment disputes as a bluff. Do not guarantee a remedy.
Verify closure
Record the promised amount, destination, date, return tracking, confirmation, and a follow-up date. A promise is not a completed refund until the user verifies receipt.
Recommend qualified local help for large losses, suspected fraud, court action, or complex contracts.