Even on a modern booking platform, agencies still do part of their day in native GDS commands — checking how a booking changed, reading fare displays, working queues, adding requests the standard screens don't cover. Rezencia puts the GDS terminal inside the admin, next to the booking.
01 · The problem
The problem
Without a built-in terminal, an agent leaves the platform, signs in to the GDS application, retrieves the booking again by its locator, does the work, then comes back to update the platform record.
- Retrieving the wrong booking
- Changing one system but not the other
- Keeping a customer waiting while juggling two applications
02 · Why it's hard to fix
Why it's hard to fix
Experienced agents think in commands
Replacing every command with a button would slow down the fastest people on the desk. The commands have to stay.
Context is lost between applications
The booking on screen has to be found again on the GDS side.
Two sign-ins, two sets of access
Every extra application has to be provisioned, secured and supported.
03 · What we built
What we built
A GDS terminal built into the Rezencia admin. Agents move from the booking record to the command line and back without switching applications. Native commands are unchanged, and because Rezencia already holds the agency's GDS connection, there is no separate application or sign-in.
04 · How it works
How it works
- 1
Open the booking
In the admin, where the agent already works.
- 2
Open the terminal
Available from the admin, alongside the booking.
- 3
Work in native commands
Commands go in and responses come back exactly as in the GDS.
- 4
Carry on in the booking
No switching back and no second application to close.
05 · What changes for the team
What changes for the team
| Before | With Voraal |
|---|---|
| Two applications open at once | One application |
| A separate GDS sign-in before every command session | The admin session the agent is already in |
| The booking retrieved a second time on the GDS side | The terminal opens from the booking itself |
| Command-line skill used only outside the platform | Command-line skill used where the booking is |
06 · What it does not do
What it does not do
- It is a terminal, not GDS training — agents need to know the commands.
- Use is governed by the agency's own GDS agreement.
- It doesn't replace every function of a GDS desktop product; it removes the need to leave the admin for work done alongside bookings.
See it on your own bookings.
