Claude gathers the facts, researches the rules and drafts the refund request email after a delayed or cancelled flight.
Claude gathers the facts, researches the rules and drafts the refund request email after a delayed or cancelled flight.
The post describes a cousin who had booked a flight through Claude using a custom MCP connector, so Claude already had the flight details in context. When the flight had a major delay, he told Claude about the disruption and asked it to check U.S. DOT rules and draft the claim request; Claude researched the delay and refund rules and said he was entitled to a refund.
The claimed result was a full ticket refund, framed as avoiding claims companies that take a large commission. In the comments, others note this was just a refund rather than extra compensation, and that some airlines may let passengers cancel in the app without waiting in line.
The main catch in the comments is that refund rules were changing again on October 19, 2026, so anyone copying this would need Claude to use the latest rules.
My flight [airline, flight number] on [date] from [origin] to [destination] was [delayed by X hours/cancelled]. Ask me any questions you need, then research which refund or compensation rules apply to this route. Finish by drafting a refund request email with the facts, the rule, the amount I'm claiming, and a reply deadline, and list the documents to attach. I'll send it myself.
Score every demo request against your ICP, update HubSpot and ping the right rep in Slack within a minute of the form submit.
Every new Zendesk ticket gets a category, priority and sentiment tag plus a draft reply in an internal note before an agent opens it.
Copilot and Claude review each PR for bugs, missing tests and risky changes before a human looks, so reviewers can focus on design.