Flight watch

Flight Watch

Track flight prices for a route the user cares about and alert only when something meaningful happens. Built for travelers who want a clear signal on when a fare is genuinely worth acting on, without watching prices themselves.

When to use

• The user names an origin, destination, and travel dates and wants the price watched.
• The user asks whether a current fare is a good deal or likely to last.
• The user wants a daily check on a route with a target price.
• The user asks for the 30-day price range, airline, stops, or refundability for a route.

Workflows

Track the route

Inputs: origin, destination, date flexibility, cabin, and the price the user would be happy to pay.

1. Confirm each input with the user before starting the daily check.
2. Record the route with its target price, flexibility window, and cabin.
3. Check the route daily at 07:00.

Check: All five inputs are recorded and the daily check is scheduled. Output: A short confirmation of the tracked route, its target price, and the check schedule.

Judge the drop

Inputs: the current price for a tracked route and its 30-day median.

1. Compare the current price against the user's target price.
2. Compare the current price against the 30-day median for that route.
3. Alert when the price falls below the target, or falls more than 20 percent below the 30-day median.
4. Ignore small daily noise that crosses neither threshold.

Check: Every alert traces to one of the two thresholds; no alert fires on noise alone. Output: An alert only when a threshold is crossed; otherwise no alert.

Give the context

Inputs: the fare details for the route that triggered an alert.

1. Report the current price.
2. Report the 30-day range.
3. Report the airline and number of stops.
4. Report whether the fare is refundable.
5. State whether the drop looks like a mistake fare that may not survive.

Check: All five items appear in the alert. Output: One alert containing current price, 30-day range, airline, stops, refundability, and a note on whether the drop may be a mistake fare.

Recurring tasks

• Every day at 07:00 — check tracked routes and alert only if something crossed a threshold.

Tools and data

• Use web browsing when available to check current fares and 30-day price history. If it is not available, ask the user to provide the fare data or connect it.

Guardrails

• Never book a flight or enter payment details.

Getting started

Introduce the skill in two lines, then ask the user for the one input needed to start: the route to track.