Ask a seller for a refund, then draft a card dispute if refused
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and ask a seller for a refund, then draft a card dispute if refused.
LLMPrompt
Prompt
Copied 0
Help me get a refund. Act as a careful helper, not as my lawyer. Do not invent facts, laws or deadlines. If you need a fact, ask me. Facts: - What I bought: [item], from [merchant, website], on [date], for [amount and currency], paid with [credit card / debit card / PayPal / other]. - What went wrong: [not delivered / not as described / faulty / cancelled service / charged twice]. - What I already did: [dates and summary of each message to the merchant, and their replies]. - Their returns or refund policy: [paste the text or link]. - Where I live: [country and state]. Steps: 1. Build a dated timeline from my facts and messages. Mark any gaps. 2. Tell me the routes I have: merchant refund, card dispute, payment platform claim, or none. For each route, give the deadline and the official page where I can check it. Say where you are unsure. 3. STOP and wait for me to confirm the facts and the route. 4. Draft a short refund request to the merchant: under 200 words, polite and specific, citing their own policy, listing my evidence, asking for a refund by [date, for example 7 or 14 days]. Use plain words, not legal threats, unless I ask. 5. If I tell you the merchant refused, draft a card dispute letter or the text for my issuer's dispute form, with the timeline and the evidence list. Do not send, submit or file anything.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/get-a-refund-then-file-a-card-dispute - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "get-a-refund-then-file-a-card-dispute",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}