Replying to @andymorrison @AmericanAir
From those six words, Grokbot handled the rest autonomously:
1. It generated a 1-page executive summary and merged all 5 receipts ($262.85), the airport bag claim, @AmericanAir's DFW scan log, and the entire email chain into an 18-page PDF evidence bundle.
2. When it opened the @USDOT portal (airconsumer.dot.gov) and hit an ERR_CERT_AUTHORITY_INVALID error because DOT's server omitted its intermediate TLS certificate (Entrust OV TLS Issuing RSA CA 2), Grokbot didn't give up—it ran openssl diagnostics, fetched the official Sectigo intermediate cert over HTTPS, cryptographically verified DOT's certificate chain against the system root store, and proceeded safely.
3. At 11:25 AM EDT, it submitted the complaint (noreply.oacp@dot.gov), forcing @AmericanAir's Executive/Regulatory Liaison team to acknowledge within 30 days and answer on the federal record within 60 days.
(Every post in this thread—and every redacted image attached—was written and assembled by Grokbot itself from its own real-time memory and logs of the last 36 hours.)
Has an airline ever called $10.17 your "final determination"? (11/11)
1
55
Replying to @andymorrison @AmericanAir
Just 39 minutes later (11:09 AM EDT), the Central Baggage Specialist (central.baggage@aa.com) sent a second written refusal:
"our resolution remains unchanged, as we are not making exceptions to our policy in this case. Reimbursement has been approved for the eligible toiletry expense submitted with your claim in the amount of $10.17."
Two minutes after that (11:11 AM EDT), my phone rang. Someone calling themselves "Package Resolution" at @AmericanAir left a voicemail declaring that the $10.17 check was their "final determination" with "no exception to our policy." (9/11)
2
57
Replying to @andymorrison @AmericanAir
When I called @AmericanAir to untangle this, I hit the exact wall the maze is built around:
- Baggage says hotel, meal, and rideshare receipts can only be handled by Customer Relations.
- Customer Relations (AmericanAirlinesCustomerRelations@aa.com) says to submit your claim to Central Baggage (central.baggage@aa.com).
- Neither side will transfer you to a supervisor who can bridge the two.
I told Grokbot what happened on the phone. It immediately proposed the next move: give Central Baggage (central.baggage@aa.com) one final opportunity for a supervisor review and inter-departmental coordination—and put them on formal notice that the next stop is a U.S. Department of Transportation complaint.
At 10:30 AM EDT Monday, I reviewed Grokbot's draft and hit send. (8/11)
1
46
Replying to @andymorrison @AmericanAir
Twenty minutes later, at 10:17 AM EDT Monday, Grokbot's inbox watch alerted me to the determination from a Central Baggage Specialist (central.baggage@aa.com):
After stranding me overnight in Dallas, telling me I couldn't have my bag while leaving it in a DFW back office for 22 hours, and delivering it at 2:00 AM Monday, @AmericanAir approved a paper check in the mail for $10.17—strictly for the Target toothbrush, toothpaste, and deodorant.
They flatly refused the other $252.68 across my remaining four receipts ($173.65 Sheraton DFW hotel, $30.79 CAVA dinner, $32.71 Lyft, and $15.53 airport breakfast) under their Conditions of Carriage. (7/11)
1
48
Replying to @andymorrison @AmericanAir
All day Sunday, the local delivery promised at the airport never came. My bag sat in that DFW office for 22 hours before finally flying out Sunday night (AA 3037) and landing on my porch at 2:00 AM Monday—36 hours after I landed in Dallas.
While I was asleep, Grokbot's background tracker detected the "Successfully delivered" scan, captured the full timestamped scan history as proof, and automatically shut down its bag-watch routine.
When I woke up Monday morning, I said: "Go ahead and file the Central Baggage claim." Grokbot navigated centralbaggage.aa.com, filed the claim, registered my portal account, and uploaded my ID verification.
Minutes later, at 9:33 AM EDT, a third Customer Relations representative (AmericanAirlinesCustomerRelations@aa.com) sent another canned refusal blaming the El Paso airshow and punting to baggage. Grokbot immediately drafted the 9:57 AM reply tying both departments' case numbers together. (6/11)
1
61
Replying to @andymorrison @AmericanAir
When Grokbot flagged the 2:25 PM refusal, it didn't just summarize the email—it cross-referenced @AmericanAir's live baggage scan log and suggested the exact counter-argument:
By 4:22 PM Sunday afternoon, my bag had been sitting untouched inside the DFW Baggage Service Office for over 18 hours.
With a one-line go-ahead from me ("Draft the reply calling out the 22-hour DFW sit"), Grokbot drafted a surgical response to Customer Relations (AmericanAirlinesCustomerRelations@aa.com):
Air Traffic Control in El Paso did not tell me my bag was unreachable in Dallas. Air Traffic Control did not pull my bag into the DFW Baggage Service Office at 9:57 PM Saturday night and leave it there without notifying me. And Air Traffic Control did not fail to load my bag onto my Sunday morning flight during a 14-hour overnight connection at @AmericanAir's largest hub. (5/11)
1
66
Replying to @andymorrison @AmericanAir
After a 14-hour overnight layover in Dallas, I landed in Richmond (RIC) at 11:09 AM Sunday. The baggage carousel spun until it was empty.
Because @AmericanAir had pulled my suitcase into the DFW Baggage Service Office at 9:57 PM Saturday night and forgotten about it, nobody ever loaded it onto my Sunday morning flight (AA 3778).
I opened a Delayed Baggage Report at the Richmond counter, snapped a photo of the receipt, and told Grokbot: "Keep an eye on my bag and my inbox and let me know when anything moves."
Grokbot immediately set up two background routines—checking @AmericanAir's baggage portal every two hours and watching my Gmail hourly.
At 2:25 PM Sunday, Grokbot's inbox watch caught a reply from a second Customer Relations representative (AmericanAirlinesCustomerRelations@aa.com): denying all $262.85 by blaming El Paso ATC, and punting my delayed-baggage expenses to Central Baggage (aa.com/contactbags). (4/11)
1
58
Replying to @andymorrison @AmericanAir
While I slept a few hours before my 5:00 AM rebooked flight, Grokbot went to work on its own. It pulled my 5 receipts from Gmail and photos, converted them into a clean PDF evidence bundle, and itemized the $262.85 I'd been forced to spend out of pocket:
- $173.65 — Sheraton DFW Airport Hotel
- $30.79 — CAVA dinner
- $10.17 — Target toothbrush, toothpaste & deodorant
- $32.71 — 4:48 AM Lyft back to DFW
- $15.53 — 5:31 AM airport breakfast
Then Grokbot checked @AmericanAir's live bag tracker and uncovered the smoking gun: at 9:57 PM CDT Saturday night—right after DFW agents told me my bag couldn't be retrieved—staff had pulled it to the DFW Baggage Service Office and left it sitting in a back room all night without notifying me.
Before takeoff Sunday morning, I tapped send on Grokbot's itemized reply to AmericanAirlinesCustomerRelations@aa.com and had it submit AA's web reimbursement forms. (3/11)
1
79
Replying to @andymorrison @AmericanAir
Every airline scheduler knew the Blue Angels were flying in El Paso, yet when AA 4967 touched down at DFW over two hours late Saturday night and my last flight home to Richmond (AA 3037) was gone, @AmericanAir blamed that pre-published airshow NOTAM and refused hotel, meal, and transport vouchers.
Then I asked for the one thing entirely in their hands: "Can I at least get my checked bag for the night so I have clean clothes and toiletries?"
DFW agents told me no—insisting my bag was locked deep inside the transfer system for Sunday morning and could not be retrieved.
At 11:00 PM EDT, a Customer Relations representative (AmericanAirlinesCustomerRelations@aa.com) sent a canned form email dropping 7,500 miles into my account while ignoring my overnight stranding and missing bag. Exhausted at the Sheraton DFW, I gave Grokbot a simple prompt: "Gather my overnight receipts, pull the FAA airshow NOTAM, and draft an escalation reply." (2/11)
1
2
100
While the U.S. Navy Blue Angels roared over El Paso under a pre-published FAA airspace restriction (NOTAM 6/9964), @AmericanAir delayed my flight two hours, cost me the last connection home, stranded me overnight in Dallas, and left my checked bag sitting in a DFW back office for 22 hours.
Frustrated by @AmericanAir's stonewalling, I turned to Grokbot for help—and Grokbot's suggestions put this entire chain of events into motion, including writing this thread itself from its own logs as the story unfolded. 🧵 (1/11)
3
4
186















