Get a $199 membership refund for slow test results by citing the provider's own agreement with ChatGPT
- Posted
- by Gokul N. (LinkedIn)
- Last checked
- Method:
- How we verify
Evidence: Described by posterThe person describes what happened in words, without screenshots or video.
Beginner-friendlyNo logins, payments or coding needed. Low risk: paste the prompt and you should get something useful.
Outcome
Gokul N.'s blood test results from Superpower took 20 days. Gokul asked ChatGPT to check the refund policy, look at the dates and email the concierge. The email cited Section 14(a) of the membership agreement, set out the timeline with Superpower's own support replies, asked them to confirm when results had actually been available, and added a fallback asking for an exception if a different policy applied. Two days later Superpower confirmed a full $199 membership refund.
Agent
Prompt Recreated prompt
The source didn't share its exact prompt, so we wrote this from what it describes.
Run this task now, exactly as written below. Everything you need is here, so start straight away and only stop if something required is missing or a rule below tells you to. Goal: Write a refund request that holds the company to its own policy after it missed its promised timeline. Fill in before running: - Company and service: [SERVICE] - What they promised and what actually happened, with dates: [DETAILS] - Their terms or refund policy (paste or link): [PASTE / ATTACH POLICY] You're not my lawyer. Stick to facts I give you, label any rule you mention as something to check against the official source, and keep the tone firm but polite. Rules: - Find the clause that applies and quote its number. - Lay out a short timeline using dates and their own support replies. - Ask them to confirm the key fact you can't see (for example when the service was actually delivered). - Add a polite fallback: if they think another policy applies, ask them to share it and consider an exception. - Show me the email before it's sent. - Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify. Output: A short, firm refund email with the clause, the timeline, the request and the fallback. You'll know it worked when: the company confirms the refund in writing.
Customize this prompt
Answer these questions and we'll put your answers into the prompt for you. You can leave any of them empty.
Your prompt
Run this task now, exactly as written below. Everything you need is here, so start straight away and only stop if something required is missing or a rule below tells you to. Goal: Write a refund request that holds the company to its own policy after it missed its promised timeline. Fill in before running: - Company and service: [SERVICE] - What they promised and what actually happened, with dates: [DETAILS] - Their terms or refund policy (paste or link): [PASTE / ATTACH POLICY] You're not my lawyer. Stick to facts I give you, label any rule you mention as something to check against the official source, and keep the tone firm but polite. Rules: - Find the clause that applies and quote its number. - Lay out a short timeline using dates and their own support replies. - Ask them to confirm the key fact you can't see (for example when the service was actually delivered). - Add a polite fallback: if they think another policy applies, ask them to share it and consider an exception. - Show me the email before it's sent. - Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify. Output: A short, firm refund email with the clause, the timeline, the request and the fallback. You'll know it worked when: the company confirms the refund in writing.
Scroll to see the whole prompt. Your answers show in green.
2 blanks are still empty: Company and service; What they promised and what actually happened, with dates. They'll stay in brackets in your prompt, so the chat tool may ask you about them.
What you type stays in this browser tab. We don't send it or save it, and it's gone when you leave the page. If you use a "Try this in" button, your answers go to that tool as part of the prompt.
Try this in:
This prompt has blanks to fill in, like [SERVICE]. We'll copy it instead of filling it in, so you can edit it before you send.
Opens in a new tab. We don't see what you send.
These links are only a shortcut. We're not affiliated with OpenAI, Google or xAI, and your results may not match the source.
Optional stronger version
Our rewrite with extra checks. The poster didn't test it.
Run this task now, exactly as written below. Everything you need is here, so start straight away and only stop if something required is missing or a rule below tells you to. Goal: Write a refund request that holds the company to its own policy after it missed its promised timeline. Fill in before running: - Company and service: [SERVICE] - What they promised and what actually happened, with dates: [DETAILS] - Their terms or refund policy (paste or link): [PASTE / ATTACH POLICY] You're not my lawyer. Stick to facts I give you, label any rule you mention as something to check against the official source, and keep the tone firm but polite. Rules: - Find the clause that applies and quote its number. - Lay out a short timeline using dates and their own support replies. - Ask them to confirm the key fact you can't see (for example when the service was actually delivered). - Add a polite fallback: if they think another policy applies, ask them to share it and consider an exception. - Show me the email before it's sent. - Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify. - List the attachments I should include (receipts, screenshots, support replies). Output: A short, firm refund email with the clause, the timeline, the request and the fallback. You'll know it worked when: the company confirms the refund in writing. Before you finish: re-read my goal and constraints, check your answer against each one, and list anything you assumed or couldn't confirm.
Source
Related cases
- Get a refused warranty exchange offered after Claude found the company's own arbitration clause (partial)Recreated promptEvidence: Described by posterPartial
Dimitri Sudomoin's $1,166 robot mop failed under warranty. After eleven weeks of 'forwarding this to our technical team', the company refused to honour the warranty and offered a final 46% partial refund. Claude's first idea, a federal warranty law angle, looked weak, but reading the terms of service it found the company's own arbitration clause: under the rules of the forum the company picked, Sudomoin's filing cost was capped at $250 and the company would bear the rest of the fees. Three days after Sudomoin filed, the company offered the exchange it had previously refused. Sudomoin describes this one as still in play.
Claude · Personal · Source date:
- Build a goodwill case with ChatGPT and get a €6,000 out-of-warranty engine replacement for freeRecreated promptEvidence: Described by poster
Thomas Weilbach's car was out of warranty, and the dealership said the only long-term fix, a full engine replacement quoted at €6,000, would be paid out of pocket. Weilbach used ChatGPT in research mode to dig into the symptoms (oil consumption, juddering under load and limp mode), known problems with that engine, service bulletins and how others had handled similar cases, testing each possible cause against the symptoms. ChatGPT then helped turn it all into a clear, structured argument. Weilbach took the case to the dealership, and the manufacturer approved the full engine replacement under goodwill at no charge.
ChatGPT · Personal · Source date:
- Work out why a meeting was missed and set up a tested email-to-calendar check with ChatGPT and CodexRecreated promptEvidence: Described by poster
Dave W Plummer missed an important appearance and asked the ChatGPT desktop app, which has access to their Gmail, to work out how it happened. It found Plummer had noon in mind, the time of an earlier prep call, while the event started at 7:50 a.m. Pacific, with emails also mentioning 8:50 a.m. Mountain. When Codex then reconstructed the email trail, it found the organiser had cancelled the calendar invite sent to Plummer's regular address while sorting out a Teams login mismatch, and the later confirmation email had no new invite. With Codex, Plummer then set up a recurring agent that reads email threads, including changes and cancellations, adds missing calendar entries with the source email and link, and flags contradictions. Test alerts at first didn't notify on the iPhone; after checking alarms, sync and Focus settings, a test finally rang. It now checks every ten minutes while the Mac is awake; its first historical review was still running.
ChatGPT, Codex · Personal · Source date: