Track booked travel price drops
Monitor already-booked flights or hotels for automated refund requests.
Track fare changes on booked flights and negotiate travel credits.
Issued airline travel credit representing the fare difference on your reservation.
"Muse had been tracking the price of a flight the author booked; when it detected a meaningful price drop on the upcoming United flight, the author gave the go-ahead, and Muse logged into the United account, chatted with United, and secured $1,000 in credit — $1,026 saved in total."
Access to the user's booked-flight information for price tracking (the post mentions having Muse track booked flights); access to the user's United account (the post says Muse logged into it).
Direct account login / web chat automation
Review authorization prompts carefully before connecting.Review generated values, dates, or messages before executing binding transactions or payments.
Gather materials: Access to the user's booked-flight information for price tracking (the post mentions having Muse track booked flights); access to the user's United account (the post says Muse logged into it).
Copy the prompt template below, substituting bracketed text like [date range] or [account details] with your real information.
Paste into your Muse session. Watch for required tool authorizations or review prompts.
Compare generated figures, dates, or communication drafts against your original records before taking binding actions.
Track the prices of the flights I've booked: [flight details / booking references]. Check prices [frequency, e.g., daily]. If any flight drops in price by more than [amount or percentage], notify me immediately with the old price, the new price, and the estimated credit — and take no further action until I explicitly say go. After I approve, contact the airline on my behalf to claim the fare difference, and report back the credit amount and confirmation details. Never make changes to a booking without my explicit approval.
Before relying on the output or confirming irreversible actions, run these targeted verification checks:
If third-party service connections fail or require permissions, inspect your account tokens.
Check Connections & permissions guide →If large context blocks cause partial truncation, break input into smaller batches.
Review token caps in Access & limits →