How a travel operating system works

The short version is this: one booking, one live record, three portals. The traveller works in My Mobility. The company works in the Client Portal. The travel team works in Control Tower. Everyone sees the same status. That is the difference between an operating system and a stack of disconnected applications.

GTOS is built on operating experience across 100,000+ trips. The walkthrough below describes the product as it is designed to run, not a theoretical architecture.

From search to a ticket

1. The traveller searches in My Mobility. Flights can be one-way, return or multi-city. The same path covers hotels and related services such as transfers, car rental, eSIM, lounges and meet and greet, in the currencies the programme uses.
2. Policy is checked on every option. Rules can be set by designation, department and destination. Each option shows whether it is within policy before the traveller selects it. Out-of-policy choices are flagged.
3. The request moves through an approval chain. Chains are taken from the organisation chart and can follow role and limit. A manager can approve in one tap, including on a phone. Out-of-policy items go to the right approver. Every decision is recorded.
4. The booking is issued. Approved, in-policy bookings can be ticketed and confirmed automatically. Complex trips go to a specialist desk rather than being forced through a fully automatic path.
5. Cost lands in finance dashboards. Spend, budgets, commitments, receipts and invoices attach to the same record. CEO, CFO and finance can see spend by department, traveller, supplier and policy compliance. USD is the main currency on this site; GTOS can record spend in more than one currency.

That path is also summarised on the platform page and in what a travel operating system covers.

The three portals in practice

My Mobility is where employees book within policy, keep trips, documents and confirmations, and complete passport and visa readiness checks. When the employee is also a manager, approvals happen in the same portal. It is built for the web and for a phone, so the next trip is available on the way to the airport as well as at a desk. See My Mobility.

The Client Portal is where admins, approvers, finance and leadership run the programme: employees and roles, the organisation chart, travel policy, approval chains, budgets, invoices and spend dashboards. See Client Portal.

Control Tower is the operations view behind every client. It shows every trip and request, including VIP, visa, group and meetings cases, with response-time tracking. The desk does not need a second briefing tool; it works on the same record the company already sees. See Control Tower and managed travel.

What the operating system is doing in the background

While the traveller sees a search screen, the operating system is applying policy, assembling an approval path, and preparing a record that finance and duty of care can use later. Once the trip is live, a traveller map can show where people are. Visa and passport checks sit on the trip. If plans change, 24/7 operations around that record give the company and the desk a way to act without starting a new email thread that has no history.

Security is part of the same design. Each company sees only its own data. Access is by role. Two-step sign-in is available on the GTOS app. Requests, approvals and changes are written to an audit trail. We do not claim certifications we do not hold. Read Security.

What this is not

A travel operating system is not only an online booking tool, although booking is in the path. It is not only an expense tool, although receipts are matched to the trip. It is not only a mid-office for agencies, although agencies and TMCs can run programmes on it and can use Voraal products such as Rezencia and Folio6 alongside. Avunzo, designed to connect travel content and booking flows to a business's own channels, is not yet live on production; early access is available on request.

GTOS is built to scale to 1,000+ employees per client. Pricing is in USD and available on request. If you want to see this flow with your own policy loaded into a demo account, book a walkthrough.