What a travel control tower is

This definition is written by the team behind GTOS, the Global Travel Operating System from Voraal, and is built on operating experience across 100,000+ trips. In the product, that operations view is Control Tower. We do not invent queue times or “trips under management” figures.

What the view is for

Programmes fail in the gap between a booking tool and a mailbox. A traveller submits a change, an adviser cannot find the latest fare, finance cannot see whether the invoice still matches, and duty of care becomes a search across inboxes. A control tower is the answer to that gap: one place to see what needs attention, and one file to work on when it does. Queues might include pending approvals, tickets waiting on data before auto-issue, mid-trip amendments, document chases, and supplier follow-up. The content of the queues will differ by desk. The rule should not: work happens on the trip, not beside it.

This is close to mid-office work, and in an agency the control tower is often where mid-office actually sits. The phrase “control tower” is used here, and in GTOS, for a slightly wider idea: it is also the view a TMC or corporate desk uses for live operations and after-hours support, not only for quality-checking a new booking.

What it is not

It is not a wall of unconnected screens. A display that cannot open the trip is a monitor, not a control tower. It is not a substitute for duty of care specialists or emergency services. It can put the current itinerary, contacts and documents in front of the people who have to act; it cannot be those people. It is not the online booking tool. Travellers book on their path; the desk works exceptions and changes in the tower. And it is not, on its own, back-office settlement, though a change worked in the tower should still be the file the invoice points at.

How GTOS uses the name

Control Tower is the GTOS operations surface for the desk. The expert desk is the human path for trips the self-serve flow cannot finish. Both are designed to write to the same record as My Mobility and the client portal. That design is the one described in how TMCs use software. A demo should start with a booking the traveller made, then open the same trip in Control Tower, make a change, and show the traveller and the client the updated file.

How to judge one

Ask what a night adviser sees when a traveller calls about a missed connection. If the answer is “the same itinerary the traveller already has,” the tower is doing the job. If the answer is “we pull the PNR and check email,” the organisation still has a desk, but it does not yet have a control tower in the sense this glossary uses. Also ask how queues are bounded by account and role, so one client’s work cannot be confused with another’s. Operations access without role-based limits is not an enterprise-ready view.