Notifications on the trip record, without named messaging platforms

GTOS is the Global Travel Operating System from Voraal, built on operating experience across 100,000+ trips. Approvers work pending requests in the Client Portal. Travellers see status in My Mobility, including as a mobile web experience on a phone. This page describes how notices may, if agreed, also reach a company messaging or mail environment — without naming those environments, and without treating a chat tool as the system of record.

In-product first

Approvals still happen on the trip. A reminder should bring an approver to that queue. A status notice should open the booking the traveller already has, not a detached copy of an itinerary. When a flight is retimed, the current confirmation on the file is what matters; a message that repeats yesterday’s times is noise.

That design already operates without an external messaging connector. Many programmes will choose to stay there, at least at the start.

The people who need a notice are not always the same people who booked the trip. An approver, a traveller, an assistant and a travel manager can each need a different prompt from the same event. Role-based access should still decide who is entitled to see that event. A forwarded message is not an access model, and it should not become one just because a reminder left the portal.

What we will and will not claim

Buyers are right to ask whether GTOS can “notify us in our messaging tool.” The accurate answer is:

- In-product notifications already exist around approvals, status and changes on the trip record.

- A connection that delivers notices into a company messaging or mail environment is an implementation topic. It is not a public catalogue of pre-certified connectors.

- We do not name messaging platforms, chat products, or mail suites on this page, and we will not invent a bot, a channel architecture, or a delivery-time guarantee.

If you need that path, bring the environment you use and the events you care about — pending approval, decision taken, booking confirmed, itinerary changed — to a demo. We will describe only what is actually available. Webhooks is the related conversation when a company system, rather than a person, should receive an event. Calendar connections are handled with the same restraint.

Access remains by role. Each company sees only its own data. Notices must not become a way to leak trips across a boundary. See Security. Two-step sign-in is available on the GTOS app. We do not claim certifications we do not hold.

USD is the main currency on this site. Pricing is in USD and available on request.