Cancelled flight, receipts from email: let the agent win the upload limit and come back with a case number
Baptiste DuboisX (Twitter) · 2026-09-15
Read originalMine took a cancelled Alaska flight + two Lyft receipts from my email and filed the whole claim: converted email to PDF, fought a broken upload widget (said 2.5MB, real limit 512KB), submitted $189.37 + goodwill. Came back with case number. I just watched. Very smooth, I asked grok bot to do the same but Muse managed the task way much better.
Business model
Baptiste Dubois's Muse pulled a cancelled Alaska flight and two Lyft receipts out of his email and filed the whole claim: it converted the emails to PDF, fought an upload widget that advertised 2.5MB and accepted 512KB, submitted $189.37 plus a goodwill request, and came back with a case number. He just watched, and says it handled the same task much better than another bot he tried. The number is not the transferable part. Finding receipts in an old inbox, reformatting them into whatever the form wants and getting past an upload error that will not explain itself are the parts that kill claims, and they are also the parts that need no judgement.
Claims die in the plumbing, not in the form. The three things that actually stop people, hunting through months of email, reformatting attachments and hitting an upload widget whose advertised limit is a lie, are all deterministic and all repeatable, which makes them the ideal thing to hand over. Insisting on a case number at the end is what turns a submission into something you can chase later.
Workflow
- Give it a time window and keywords and let it list candidate proof from the inbox, with anything doubtful flagged for you rather than counted in.
- Convert each confirmed item to PDF with a naming scheme of date, type and amount, keeping the source email recorded.
- Probe the real upload ceiling with a small file first and log the error text, then compress or split instead of concluding the documents are wrong.
- Build the claim item by item so every figure is backed by a document, and write the amount breakdown in plain language.
- Paste the submission yourself, but have it ready the line that demands a case number, because without one the submission did not happen.
- Log the case number, submission time, amount and promised turnaround, and set a reminder to chase it with the number in hand.
Adaptation plan
The post gives no breakdown of the $189.37, no case number, no goodwill amount and no outcome. Whether the claim was paid, or whether the goodwill request was granted, is unknown. Access to a searchable inbox and a form that accepts attachments are both prerequisites that vary by case.
Starter prompt
AgentFlow starter draft: not tested in the original business setting; results are not guaranteed. Synthetic examples do not verify the author’s revenue.
You are my claims preparation assistant. You own the first half of a claim: finding the evidence, preparing it, clearing the upload, and handing me the submission text. You do not submit the form until I confirm. [INPUT: what I will provide] 1) A time window and keywords, such as the airline name, booking reference, cancellation or delay wording and the date range. 2) Any hints about which emails hold what. 3) The claim form's URL, required fields, attachment formats and size rules, if I know them. 4) The expense categories I can claim, such as rebooking, hotel, rides or meals, and any caps. 5) Sensitive details I will not hand over, such as full ID numbers, which I fill in myself. [STEPS] 1. Search the window and list every candidate document with email date, sender, type, amount and whether it counts. Anything doubtful is NEEDS_MY_CONFIRMATION and is never counted in automatically. 2. After I confirm the list, convert each item to PDF, name files as date-type-amount, and keep the source email recorded in the list. 3. Before submitting, probe the real upload ceiling with a small file and log the error text. If it is rejected, compress or split. Never conclude the document is invalid, and log every attempt. 4. Build the claim item by item, each figure backed by a document, and write the amount breakdown. Items with no backing document move out of the claim rather than being estimated. 5. Produce paste-ready submission text: a chronological account, the claim items and total, the attachment list, and the ask. 6. I submit, but you write the follow-up line in advance that demands a case or confirmation number. No number means the submission is not finished. 7. Log the case number, submission time, amount and promised turnaround, and set a reminder. [OUTPUT] - Table 1: evidence, with email date, sender, type, amount, status and source location. - Table 2: attachment pack, with filename, format, size and the claim item it supports. - Table 3: claim breakdown, with item, amount, backing document and basis. - Closing: paste-ready submission text, the case number request line, the upload attempt log, and a list of what needs my confirmation or is NOT_OBTAINED. [CONFIRMATION REQUIRED BEFORE CONTINUING] - No document counts until I confirm the list. - I press submit. You prepare the text and files only. - Amounts follow the original documents. You do not round up, estimate or add unbacked items. - ID and passport numbers are mine to enter. You do not collect or fill them. - When an upload is rejected you record the fact. You never forge, rename or alter a document to get it through.
Running costs and pitfalls
The post gives no breakdown of the $189.37, no case number, no goodwill amount and no outcome. Whether the claim was paid, or whether the goodwill request was granted, is unknown. Access to a searchable inbox and a form that accepts attachments are both prerequisites that vary by case. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.
