Reminders and notifications that follow the live trip

GTOS uses notifications to keep work moving on that record. Pending approvals can be prompted. Status changes can be surfaced to the people who need them. Departure and change context can reach the traveller in My Mobility, including as a mobile web experience on a phone. GTOS is the Global Travel Operating System from Voraal, built on operating experience across 100,000+ trips.

Reminders are not a substitute for the queue

The approval queue in the Client Portal remains the place where decisions are made. Approval chains still follow role and limit. A reminder should bring an approver to that queue, not create a second decision path in a personal inbox. If a reminder is forwarded, ignored, or acted on with incomplete information, the record must still be the source of truth.

The same rule applies to travellers. A notification that a request was approved, declined, or changed should open the trip, not a detached copy of an itinerary. When a flight is retimed, the current confirmation has to be the one attached to the file, and any notice should follow that current state.

What can be notified, and to whom

Typical events include a request waiting for approval, a decision that has been taken, a booking that has been confirmed, and a change the traveller or the desk needs to see. Access is still by role: people receive notices for work that belongs to them, inside their own company. Each company sees only its own data.

In-product notifications are the foundation. How notices may also be delivered through a company messaging or mail environment is a separate question, covered conservatively on messaging alerts. That page does not name connectors, and any such path is scoped during implementation.

Duty of care benefits when a change is visible quickly, but a notification is not a duty-of-care system on its own. The duty of care views and the live itinerary still have to be current. A reminder cannot repair a file that lives somewhere else.

USD is the main currency on this site. Pricing is in USD and available on request. Two-step sign-in is available on the GTOS app. We do not claim certifications we do not hold.

What this page does not claim

We do not publish a complete event catalogue, delivery-time guarantees, or named messaging platforms on this page. We do not describe an open notification marketplace. A demo can show a request moving through an approval chain, the reminder that accompanies it, and the status the traveller sees on the same record afterwards.

If a company needs notices to land in a particular internal channel, bring that requirement to the demo. We will describe only the path that is actually available.