How an online booking tool works in a live corporate programme
An online booking tool, in practice, is not a consumer flight site with a company logo attached. In a corporate programme it has to apply policy at search, take an approval, issue what is already in policy, and still leave a file the desk can take when the trip is no longer self-serve. If it only searches inventory, travellers will use it until the first exception, and then the programme will split.
This guide 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 GTOS, the traveller path is My Mobility, including as a mobile web experience on a phone, not as a claimed native app-store listing. Policy-checked search marks options before a selection is made. Approved, in-policy bookings can be issued automatically. Complex work can be handed to an expert desk on the same record. Related comparisons are OBT versus TMC platform and managed versus self-serve.
What has to work, or travellers will leave
The path has to be usable. If an in-policy return takes longer, or is less clear, than a consumer booking, volume will leak. Approvers have to be able to decide without a long exchange, including on a phone. Confirmations have to be findable on the trip, not only in a personal inbox. These are practical tests, not aesthetic ones.
The path also has to be trustworthy. The policy check the traveller sees should be the one the approver and finance later see. If those views disagree, unofficial booking will feel safer than the official tool.
What an OBT should not be asked to do alone
It should not be the only place a group movement, a visa-dependent itinerary, a VIP change, or an after-hours disruption is handled, unless a specialist can take the same file. A self-serve-only design fails on those cases. A managed-only design fails on everyday volume. In practice, a programme needs both modes on one record.
Content sourcing — including any GDS or NDC path — is a scoped conversation around that record, not a substitute for it. We do not publish certified connector lists on this guide.
How to evaluate a tool in a demo
Walk a routine in-policy trip from search to ticket, on a phone if that is how your people book. Walk an out-of-policy exception. Walk a change after the ticket exists, with the desk on the same file. If any of those three requires a second system, the OBT is not yet a programme path.
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 claim certifications we do not hold. We do not invent booking-time benchmarks. Your own walkthrough against your policy is the test that matters.
Frequently asked questions
Is an OBT the same thing as a travel operating system?
No. An OBT is the booking path. A travel operating system also holds approvals, spend, duty of care and desk servicing on the same trip record. Some products only do the first job.
Should every booking stay self-serve?
No. Routine in-policy volume should. Complex, VIP, group or after-hours work should be able to move to a desk without leaving the record.
Do you claim a native mobile app in this guide?
No. In GTOS, My Mobility is a mobile web experience, including use from a phone home screen, rather than a claim about a native app-store listing.
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