Get a $1,373.97 refund for a changed flight via a bank chargeback, on Grok Bot's advice
- Posted
- by @weird_ceo
- Last checked
- Method:
- How we verify
Evidence: Described by posterThe person describes what happened in words, without screenshots or video.
Disclosure: This is our product: realagentcases is run with Grok Bot. Included because the source is public and verifiable.
Outcome
After an airline schedule change, a traveller asked for a full refund on two China Eastern tickets booked through an online travel agency; the agency confirmed it in writing on Sep 8 but then stalled through 8 complaint emails. Grok Bot advised him to stop waiting and dispute the charge with his bank. On Oct 11 the bank ruled in his favour and he got the full $1,373.97 back.
Agent
Prompt Recreated prompt
The source didn't share its exact prompt, so we wrote this from what it describes.
Let's work this out together. I'll tell you what I know, you suggest options and ask what you need, and we'll narrow it down step by step. Nothing gets booked, bought or sent until I say so. Goal: Decide how to get a refund a travel company promised but hasn't paid, and prepare the strongest route. What I'll share as we go: - Booking details, amounts and dates - The written refund promise - Every complaint email and chat reply - How I paid (card type, bank) Rules: - Build a dated timeline from my documents. - Compare options: keep chasing, regulator complaint, card chargeback, with time limits for each. - Draft the chargeback explanation with the written promise attached. - Show me anything before it's sent or submitted. - If a site asks for a login, a CAPTCHA or payment details, stop and hand control back to me. - Ask for my OK before you pay, book, send, submit or cancel anything. - 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 timeline, a recommended route with deadlines, and a ready-to-file dispute text. You'll know it worked when: the dispute is filed before the deadline with clear proof of the promised refund.
Try this in:
Sends the Recreated prompt shown above. ChatGPT and Grok open with it filled in, and ChatGPT may send it straight away. Gemini opens empty, so we copy the prompt for you to paste. Every button also copies it.
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.
Let's work this out together. I'll tell you what I know, you suggest options and ask what you need, and we'll narrow it down step by step. Nothing gets booked, bought or sent until I say so. Goal: Decide how to get a refund a travel company promised but hasn't paid, and prepare the strongest route. What I'll share as we go: - Booking details, amounts and dates - The written refund promise - Every complaint email and chat reply - How I paid (card type, bank) Rules: - Build a dated timeline from my documents. - Compare options: keep chasing, regulator complaint, card chargeback, with time limits for each. - Draft the chargeback explanation with the written promise attached. - Show me anything before it's sent or submitted. - If a site asks for a login, a CAPTCHA or payment details, stop and hand control back to me. - Ask for my OK before you pay, book, send, submit or cancel anything. - Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify. - Check my card's chargeback deadline first, counted from the date of the promise or the charge. Output: A timeline, a recommended route with deadlines, and a ready-to-file dispute text. You'll know it worked when: the dispute is filed before the deadline with clear proof of the promised refund. 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
https://x.com/weird_ceo/status/2109664238818164876
Related cases
- Ask airlines to refund late-night rides after delayed flights with Meta's Muse, which drafted good emails but missed that airlines don't take email (partial)Recreated promptEvidence: Article or interviewPartial
Gizmodo's Webb Wright had some badly delayed flights that forced them to pay for Lyft rides home in the early hours, and asked Muse to request refunds. Given screenshots of the receipts and the flight details, Muse drafted decent emails, courteous but firm. But buried inside one draft was the important point that the airlines didn't take refund requests by email, so the drafts would have to be pasted into the airlines' websites. Webb ended up opening a browser and entering the details by hand, though they did use the message Muse had drafted.
Muse · Travel · Source date:
- Claim compensation for a long flight delay (EU261) with ChatGPTRecreated promptEvidence: Described by poster
After a Norse Atlantic flight from Oslo was delayed overnight and the airline offered a $25 refreshment card, then ignored his claims, the author pasted the delay email into ChatGPT Pro and asked about his rights. Over eleven months it walked him through EU261 (600 euros per passenger for four people), the national complaint body, the Norwegian conciliation court and a settlement including statutory interest; on July 14, 2026 the airline wired $4,760.36.
Poster says:$4,760.36 paid after eleven months
ChatGPT · Travel · Source date:
- Win a Lufthansa refund for a cancelled trip over months of ChatGPT-written emailsRecreated promptEvidence: Described by posterPartial
After a Lisbon–Frankfurt–Miami flight was delayed, boarded and then cancelled, the poster gave up the trip and flew elsewhere. Lufthansa tried to charge for the Lisbon–Frankfurt leg and offered only 'the difference'. The poster fought it entirely by email using ChatGPT, and after months and a long chain of emails got the refund. They still lost money, days and the trip with their mother.
ChatGPT · Travel · Source date: