Tracking several routes at once without drowning
Twelve active alerts are not better than two. They are worse — because you stop opening them. Here is how to run a watchlist that stays readable.
One alert per trip, not one alert per daydream. That is the rule separating useful monitoring from a folder of emails you archive unread — and most people discover it after missing a genuine opportunity, buried under nine notifications that were not.
How many alerts before it tips over?
The problem is not the number of alerts. It is the number of notifications you do not act on.
An alert you react to half the time sustains your attention. An alert you never react to drains it — and it drains the one next to it too, because you stop opening the message before you have seen who sent it.
The test is simple: if you would not book at the price you set, the alert should not exist. Wanting to travel somewhere is not a trip.
What a too-broad alert becomes
"Montreal → anywhere in Europe, under $900" sounds clever. It is the opposite.
That filter fires on every ordinary dip across thirty-odd routes, twenty-five of which do not interest you. You get volume, never a decision. And the day Lisbon drops to $480, the line is lost among the others.
An alert has to be narrow enough that firing is an event.
How to structure a real watchlist
Three categories are enough, and they do not share a lifespan.
- Committed: a decided trip, fixed dates, firm budget. Narrow alert, watched until purchase, then deleted.
- Recurring: the route you fly every year — family, the cabin, the old country. Budget anchored to the usual price, alert left running in the background.
- Opportunistic: a destination you would take at the right price, no fixed date. One at a time. This is the category that overflows and contaminates the other two.
The budget is the real filter
Across a watchlist, the budget does the sorting, not the number of alerts.
A budget set at the route's usual price fires constantly. A budget set far below it never fires. The right setting is the price at which you would reach for your card tonight — not the one that would please you.
Set that threshold once, honestly, and the alert stays silent until it matters. The full method is in setting an honest budget threshold.
Prune every quarter
An alert is not forever. Dates pass, plans change, budgets age with the market.
Three questions, four times a year: is this trip still on? Does this budget still match the route's current price? Have I reacted to this alert at least once in three months?
A no to the third is enough to delete it. That is not waste: it is what keeps the others readable.
What it looks like in practice
Two to four well-tuned alerts beat twelve broad ones — every time. It is also why Kestrelia's plans cap the number of alerts rather than selling them by the unit: past a handful, value falls instead of rising.
To work out where to set each threshold, the Tuesday myth explains why a price can only be judged against its own route's history.