Book and open a corporate trip on a phone, as a mobile web experience

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. The product pages for mobile and My Mobility describe the traveller path. The travellers solution page covers the wider experience. We will not claim an app-store product, a device-native notification badge, or offline features we do not have.

1. What a traveller should be able to do on a phone

They should be able to start or follow a request, see policy-checked options, and submit that request for approval where one is required. They should be able to open the current ticket, hotel confirmation and related documents without writing to a coordinator. They should be able to see status when a plan changes. If any of those jobs still depend on a forwarded email, the mobile experience is not yet doing the work.

The booking path is still a corporate path. Travel policy applies on a phone in the same way it applies at a desk. A mobile request is not a way around the rules.

2. Why mobile web, and why that distinction matters

Native apps and mobile web are not the same product. A native app implies store listings, install cycles and device-level capabilities that this guide will not invent. A mobile web experience means the traveller opens My Mobility in a browser, signed in, and works the live record. That is the claim to test in a demo: can a traveller complete a routine in-policy request, and later open the current confirmation, on a phone?

Approvers may also need to act on a request away from a desk. The same honesty applies. If an approver can review cost and policy and take a decision on a phone, that should be shown, not assumed. If a particular action still requires the full Client Portal on a larger screen, that limit should be stated.

3. Changes, duty of care and the current file

The hardest mobile moment is a retimed flight at an airport. The confirmation the traveller opens has to be the current one, and the desk has to be looking at the same file. Mobile web is useful here only because it is a window onto the record, not because it is a separate itinerary store.

USD is the main currency on this site. Pricing is in USD and available on request. Each company sees only its own data. Access is by role. Two-step sign-in is available on the GTOS app. We do not claim certifications we do not hold.

A demo should include a booking or a document lookup on a phone, on purpose. If your travellers have been asking for “the app,” use that session to show what the mobile web path actually does, and to be clear about what a native app would be if it is not part of the product today.