At a glance
- The situation
- A mid-size agency has sold and ticketed a family's return trip; the airline cancels the outbound sector the evening before departure.
- What goes wrong
- The change sits unseen in a GDS queue overnight, the airline sends the family back to the agency, and the booking record drifts out of step with the airline until a refund is blocked as a "no-show".
- What changes
- The platform collects the change into a schedule-change queue, alerts the family through the agency's own channels and lets an agent reissue or refund from the booking, so the agency acts first.
An illustrative scenario: a mid-size agency sells a return flight; the airline cancels one sector shortly before departure and the traveller is bounced between airline and agency. With a schedule-change queue, proactive passenger alerts and one-click reissue, the agency becomes the party that acts first instead of the party that gets blamed.
The scenario
Picture a mid-size agency that sells a return trip for a family of four. The tickets were issued weeks ago through the agency's own GDS credentials, the payment is settled and the booking has dropped out of everyone's mind. Late on the evening before departure the airline cancels the outbound sector because of an aircraft swap.
The family hears about it first, from the airline app. They call the airline and are told that the ticket was issued by a third party, so the agency has to handle any rebooking. They call the agency's line, which is closed for the night. They try the agency's social media inbox. By morning they have bought new tickets themselves at the airport counter and posted about the experience publicly.
Inside the agency, nobody did anything wrong on purpose. The cancellation message landed in a GDS queue that nobody was watching overnight. The airline had already moved the booking to a protected flight the family could not use, and the record in the agency's own system still showed the original itinerary. The agent who opens the queue in the morning sees a change that is already a day old and a family that has already travelled.
The damage keeps going after the trip. When the family asks for the unused coupons to be refunded, the airline's record shows the passengers did not fly the protected flight, so the coupons read as a no-show. The agency now has to prove, weeks later, that the airline cancelled first — a dispute that costs more staff time than the original booking earned.
Why it is hard to fix
Airlines hand servicing back to the seller
Once a ticket is under agency control, the airline usually expects the agency to rebook or refund it — even when the traveller calls the airline directly.
Changes arrive as queue messages
Schedule changes and cancellations land in GDS queues and airline notifications that someone has to notice, read and act on, in the right order, before departure.
Status drifts apart quickly
If the agency record is not updated when the airline changes the flight, the coupon status, the traveller's expectations and the refund rules all start to disagree.
The worst changes happen out of hours
Operational cancellations cluster in the evening and overnight, exactly when a small servicing team is not at its desk.
What changes with the platform
On the Innovate Solution platform, airline schedule changes and cancellations are collected into a schedule-change queue instead of being left inside the GDS. Each item shows the booking, the old and new flight side by side, the travellers affected and what the agent can do next: accept the airline's protection, rebook onto an alternative, or refund.
At the same moment, the traveller can be told through the messaging channels the agency uses — WhatsApp, SMS or email through Inno Message — that the agency knows about the change and is working on it. That single message changes who the family believes is in charge.
The reissue or refund itself is one click from the booking, so the agency record, the ticket coupons and the traveller's itinerary are brought back into line in the same action. For the cases that still need a cryptic entry, the integrated GDS terminal sits inside the same screen, and the platform's 24/7 support answers within three minutes if the agent needs help.
How it works, step by step
-
The airline changes the flight
The cancellation reaches the platform from the GDS queue and appears in the schedule-change queue against the right booking.
-
The traveller is told first by the agency
A proactive alert goes out through the agency's own messaging channels, so the family hears from the seller before, or at the same time as, the airline app.
-
An agent works the queue item
The agent sees old and new flights, the fare rules and the alternatives, and chooses to accept the change, rebook onto a better option or refund.
-
The ticket is reissued or refunded
Reissue or refund runs from the booking with one click; the coupon status and the agency record update together, so no "no-show" can appear later.
-
The traveller gets the new itinerary
The updated itinerary goes out on the same channel as the first alert, closing the loop before anyone needs to call.
-
The queue item is closed with a trail
The booking keeps the full history — the airline's change, the agency's action and the messages sent — ready if a refund or dispute follows.
Before and after
| Before | With the platform |
|---|---|
| The traveller learns about the cancellation from the airline and is sent back to the agency | The agency sees the change in its queue and contacts the traveller itself |
| Changes wait in a GDS queue until someone happens to look | Changes are collected in one platform queue with a clear next action |
| The agency record still shows the old flight | The record is updated when the change is accepted, rebooked or refunded |
| Every rebooking needs a specialist and a separate terminal session | Reissue and refund start from the booking; the integrated terminal is there when needed |
| A later refund dispute is argued from memory and old emails | The booking history shows who changed what, when, and what the traveller was told |
What it does not do
- It cannot stop an airline cancelling or changing a flight, and it cannot make an airline offer alternatives it does not have.
- It does not decide on the traveller's behalf whether to accept a change; the agency and the traveller still choose, and refund eligibility still follows the airline's fare rules and any regulation that applies to the route.
- Alerts go out only through the channels the agency has connected and the contact details on the booking.
Questions about this scenario
In this scenario, why did the airline send the family back to the agency?
Because the ticket was issued by the agency, it was under agency control. Airlines commonly expect the seller to service such tickets, which is why the agency needs to see the change as early as the airline does.
What would have prevented the "no-show" dispute?
Acting on the cancellation while it was still in the queue: accepting, rebooking or refunding it so the booking record matched what the airline had done before the departure time passed.
Does the agency need a night shift to make this work?
Not necessarily. The queue keeps every change waiting with its booking context, and the traveller alert tells the family the agency is aware, so the agent who picks it up next has everything in one place. Agencies with high volume may still choose to staff an evening desk.
What if the booking was made through NDC or a low-cost carrier rather than the GDS?
The same queue collects changes from NDC orders and low-cost bookings, so the agent works one list regardless of where the ticket was issued.
Related
About this page. This is an illustrative scenario: the business is hypothetical and the story is drawn from problems that travellers and travel agents describe in public forum discussions. It contains no customer names and no performance figures. The problem itself is explained on Flight disruption management; for measured results from named customers, see the case studies.
Recognise this situation? We will walk through it on the platform with your own bookings. The full explanation of the problem — causes, approach and limits — is on Flight disruption management.
