Dots to reroute a delayed Amsterdam connection
Denis Shiryaev reported an Alaska Airlines delay that put an Amsterdam connection at risk. Dots used its own computer to chat with Alaska, Delta and KLM concurrently, found another route and, according to the author, rebooked without an extra charge after he approved.
x.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Contact the airlines about this disrupted connection, find a replacement route for my approval, and verify ticket, cabin and baggage status separately.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Denis Shiryaev (@literallydenis)
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- A reported no-extra-charge Seattle–Munich–Amsterdam rebooking with confirmed ticket and cabin; baggage arrival timing remained unresolved.
- Human involvement
- Shiryaev approved before the rebooking.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Coordinate with the airlines after the disrupted connection.
- Present the replacement route for approval before rebooking.
- Report ticket, cabin and baggage status separately, including unresolved checks.
Denis Shiryaev reported an Alaska Airlines delay that put an Amsterdam connection at risk. Dots used its own computer to chat with Alaska, Delta and KLM concurrently, found another route and, according to the author, rebooked without an extra charge after he approved.
The attached original screenshot supplies details beyond the short post. KLM provided a reissued ticket number and confirmed business class on both replacement flights. The displayed route was Lufthansa from Seattle to Munich, followed by Munich to Amsterdam. The screenshot also states there was no additional charge; it does not show an independent payment statement.
Baggage needed its own follow-up. The agent reported that Alaska Baggage had confirmed the suitcase remained checked through to Amsterdam. The traveller would not need to collect it in Seattle or leave the transit area for it. However, the airline had not confirmed that the bag would arrive at the same time as the passenger.
The agent still planned to check where new boarding passes could be obtained and check the gate. Those lines describe pending work, not completed checks. This account is useful because the handoff separates a confirmed ticket and cabin from an unresolved baggage question. The human approval is explicit, while actual arrival and eventual bag delivery are not reported.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: x.com · Denis Shiryaev (@literallydenis)
Frequently asked questions
Was the replacement booking approved?
Yes. The author explicitly says rebooking followed his approval.
What did the screenshot confirm?
A reissued ticket number and business class on both flights.
Was baggage arrival settled?
No. Through-checking was confirmed, but simultaneous arrival was not.
More details
About this account
Dots contacted three airlines and arranged the reported replacement booking.
Firsthand source opened and read. Suggested prompt written by us from the reported workflow; no original task prompt is quoted.
Credit: Denis Shiryaev (@literallydenis)
Source published
Added to Agents In Use
Source checked
Tools and topics
Alaska Airlines · Delta · KLM · Lufthansa
Flight disruption · Multi-airline rebooking · Baggage handoff
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.