The flight moved at 3am. What should your travellers wake up to?
Airlines do not reschedule at a convenient hour. The email lands at 03:40, addressed to whoever made the booking — usually you, not the traveller. By the time your office opens, twelve people have already left for the airport on the old time.
The damage is rarely the delay itself. It is the four hours in which the traveller knew nothing and you knew everything.
What a good overnight response looks like
The sequence that works is boring, which is the point:
- Detect the change the moment the airline publishes it, not when someone reads an inbox.
- Work out who it actually affects. A change to one leg does not affect every traveller on the file — only the ones ticketed on it.
- Send the new facts — new time, new terminal, whether the connection still works.
- Say what happens next, even when the answer is "we are looking at it".
- Escalate to a human for anything that needs a decision: a missed connection, a booking that now needs reissuing.
Steps 1 to 4 do not need a person. Step 5 always does.
Say only what you know
The temptation, at 3am, is to reassure. Resist it. "Don't worry, your connection should be fine" is the single most expensive sentence in travel operations, because it converts an airline's problem into your promise.
Compare:
Your flight IB6842 has moved from 09:15 to 11:40 on 14 September. Your connection in Madrid is now 55 minutes, which is below the airport's 60-minute minimum. We are looking at alternatives and will come back to you before 09:00.
Every clause is a fact or a commitment with a time on it. Nothing is invented. The traveller can act on it — and, importantly, so can the colleague who picks this up in the morning.
The connection rule most tools get wrong
When a first leg slips, the question is never "is the delay big?" — it is "does the connection still stand?" That depends on the minimum connecting time at the specific airport and terminal pair, which is published, and which changes between terminals at the same airport. It also depends on getting the timezones right on both legs — see timezones and the traveller's clock.
A ninety-minute delay with a four-hour layover is a non-event. A twenty-minute delay with a seventy-minute layover in a different terminal is an emergency. Any system that alerts on delay length alone will page you for the first and stay silent on the second.
Who else needs to know
For a leisure booking, the traveller. For anything organised, more:
- The group leader, who is going to be asked by everyone else.
- Parents, if the travellers are minors — they will hear about it within minutes anyway, and hearing it from you first is worth a great deal.
- The ground supplier whose transfer is now meeting a different flight.
On an organised departure, the group leader's own view is what stops this becoming twelve separate conversations — see groups, leaders and rooming.
That last one is the one most often missed, and the one that costs money.
What to automate, and what never to
Automate detection, the impact check, and the first factual message. Those are mechanical, they are needed at 3am, and they are exactly what a person does worst while half asleep.
The full schedule of what goes out automatically is in what the concierge sends, and when.
Do not automate the decision. Rebooking, goodwill, and anything involving money should land in a human queue with the context already assembled. The goal is not a system that handles disruption without you. It is a system that means nobody learns about the disruption from the departure board.
The concierge in this article is how Viaquo handles schedule changes: it watches every ticketed segment, checks connections against published minimums, tells only the affected travellers, and escalates the rest to your team.
