From search to ticket: how a corporate booking flow should run
From search to ticket should be one story, not three. In a broken programme, the traveller searches in one place, an approver decides in email, and a ticket is issued in a third tool. By the time a confirmation exists, no one is sure which policy check was used, and the desk does not have a file. This guide explains a corporate booking flow that stays on one record from the first option to the issued ticket, and then through a later change.
It is written by the team behind GTOS, the Global Travel Operating System from Voraal, and is built on operating experience across 100,000+ trips. How a travel operating system works is the wider walkthrough. This page is the booking-flow slice.
1. Search with the policy already in view
The traveller searches in My Mobility. Each option can show whether it is in policy for that person's designation, department and destination, before it is selected. One-way, return and multi-city flights, hotels and other programme services can sit in the same path. If the policy check is only applied after a fare is chosen, the flow has already missed its best moment.
2. Approve with cost and policy on the same request
The request goes to the person who is allowed to decide, from the organisation chart, with a role and a limit. They see the itinerary, the estimated cost and the policy check, including on a phone. Out-of-policy choices are flagged, not hidden. The decision is written to the trip. If this step is a forwarded screenshot, the ticket that follows will be hard to explain later.
3. Issue what is already agreed, or hand the same file to a desk
Approved, in-policy bookings can be issued automatically, so the flow does not wait in a second queue. Complex, VIP, group or incomplete cases can move to an expert desk in Control Tower without the traveller starting again. The ticket and the confirmation then sit on the same record as the search and the approval. Documents are available to the traveller, the company and the desk.
4. Keep the flow open after the ticket exists
A retimed flight or an extended stay should update the same file, including after hours. Finance should still be able to match invoices to the current trip, not only to the first ticket. A demo can walk this exact sequence on a sample policy: search, exception or in-policy approval, issue or handoff, then a change, which is the test of whether the flow is really one record from first search to later change.
USD is the main currency on this site. Pricing for GTOS is in USD and available on request. Each company sees only its own data. We do not invent booking-time benchmarks or certification marks. We do not claim content-source badges in this guide; those conversations are scoped separately.
Frequently asked questions
Does every in-policy booking have to wait for a desk?
No. Approved, in-policy bookings can be issued automatically. The desk is for cases that need judgement or later change work.
Is this flow only for flights?
No. Hotels and other programme services are designed to sit on the same trip record as the flights they belong to.
Where does policy compliance get recorded?
On the trip, at the moment of search and approval, which is what later spend and audit views should use.
Related
See GTOS in a demo
We are now taking early-access requests. Demo accounts are available now.
- A walkthrough of the Client Portal, My Mobility and Control Tower
- Your travel policy, set up in a demo account
- USD pricing discussed on request, with PKR quotes available
Prefer email or WhatsApp? insights@goglobal.pk · +92 320 4111222