Map the responsibilities of separate flight tickets
Using Claude where available: Supply fictional segments, ticket groups and terms to list each supplier, responsibility and open question.
Execution environment and usage
AI / software
General text chat (example: Claude); original stack retained below
Where to operate
A general text conversation, for example a new chat at claude.ai where available. This is the suggested exercise entry, not an attribution of the original tool.
Getting started
- Open claude.ai or another text-chat tool you are authorized to use.
- Convert the required material below into readable, source-labeled text and paste only necessary authorized excerpts.
- Enter the case prompt and check the resulting draft against the original material.
Setup and plan requirements
Fictional flight segments, booking groupings and supplied terms. Live workflow separately needs provider integration and authorization. Text chat requires an available account and allowance; Claude has location and age requirements. Manually transcribe images or scans first rather than assuming text chat can inspect the original file.
Prompt portability limits
Ticket-boundary comparison needs no booking connection and cannot establish live availability or protection.
Usage limitations
This review performed no installation, hands-on test or regional-availability check. Founder Reddit page retrieved; supplied record names Claude and LetsFG.
Environment sources
適用情境 / When to use
Use the table to identify connection, baggage and change conditions that need supplier confirmation. Separate tickets do not establish protected connections. Supplied-data comparison needs no LetsFG integration and does not check live seats or book. The founder also says the system then could not modify or cancel existing bookings; this is a vendor account.
步驟 / Steps
- Prepare fictional segments, ticket groupings, time zones and supplied terms summaries.
- Map segments to bookings, separating shared reservations from independent tickets.
- Flag connection, baggage and change responsibilities for supplier confirmation.
提示詞 / Prompt
Using [fictional flight segments/ticket groups/dates and time zones/supplied fare terms/connection needs], build an itinerary-boundary table. Retain suppliers and responsibilities per ticket; flag unknown connection protection, through-baggage and change terms. Do not rank on total price alone. Compare supplied data only; do not book or assume free rebooking.
留意事項 / Cautions
- Do not give visa or travel-law conclusions.
- Do not buy, cancel, change tickets or provide payment details.
- Hong Kong and Macao are absent from Claude’s current support list. Taiwan is listed, but features, plans and external services need separate checks. This supplied-data exercise does not bypass regional restrictions.
來源限制 / Evidence limits
Savings and reliability algorithms are not independently verified; separate tickets do not establish protected connections.
流程說明 / Workflow note
These steps and prompts are original, untested exercises by this site, not the author’s verbatim workflow. Reported results do not guarantee exercise outcomes.
原始工具組合 / Original tool stack
Claude; LetsFG
Source checked: 2026-10-20