Skip to content
Voraal

Services · GDS, NDC & airline

A GDS booking system your reservation staff can work in all day

A GDS booking system is the screen where agents create, hold, change and track flight reservations that live in Amadeus, Sabre or Travelport. Rezencia gives reservation desks a graphical PNR workspace with holds, time limits, queues and readable fare rules, plus a terminal for the commands experienced agents still prefer.

Built for

  • Reservation and ticketing desks
  • Corporate travel teams (TMC)
  • Umrah and group desks
  • Branch agents
  • Sub-agents booking through a consolidator

In brief

What is a GDS booking system?

A GDS booking system is agent-facing software for managing flight reservations held in a GDS. It lets staff search, hold and book, import existing PNRs, track ticketing time limits, work airline queues, add special service requests and read fare rules without memorising cryptic commands. Voraal's Rezencia provides this as part of its reservation system, connected to the agency's own GDS office.

By the Voraal team · Updated

Reservation management, not just a search box

Most flight booking software is judged on its search results. A GDS booking system is judged on everything that happens to a reservation after it is created: the hold that is about to expire, the passenger who needs a wheelchair, the passport that was entered wrongly, the group that needs splitting, the airline that moved a departure by two hours. These live in the PNR, and agents have traditionally handled them in a terminal using commands they learned over years.

Rezencia mirrors each PNR into a booking record. The booking shows segments, passengers, fare, ticketing status and time limit in plain language, and every change made from Rezencia is written back to the GDS. When an agent needs to do something the graphical screen does not cover, the integrated GDS terminal opens from the same booking, so nobody has to retrieve the record a second time in another application.

The reservation lifecycle, as an agent sees it

Each PNR state needs a different action. The booking system's job is to make the state obvious and the next action one click away.

Reservation stateWhat the agent sees in RezenciaTypical next action
Held, unpaidCountdown to the ticketing time limitCollect payment or release the seats
Held, time limit closeBooking flagged on the desk's work listIssue, extend if the airline allows, or cancel
TicketedTicket numbers per passengerSend itinerary and invoice
Schedule change postedOld and new times side by sideAccept, reissue or refund
Segment unconfirmed or waitlistedStatus code explained in wordsChase, rebook or cancel
CancelledReason and user recordedClose or rebook

How a booking moves through the desk

  1. 01

    Create or import

    Agents book from search, or import a PNR created elsewhere by record locator. Imported PNRs become normal bookings with the same tools.

  2. 02

    Add passenger details

    Names, contacts, passport and travel document data, frequent-flyer numbers and service requests such as meals or wheelchair assistance are entered in forms and sent to the PNR.

  3. 03

    Hold and track

    The ticketing time limit is read from the PNR and shown on the booking and the desk's work list, so holds are not lost in an inbox.

  4. 04

    Check the conditions

    The fare rule is shown as a readable summary from AI fare-rule reading, with the filed text one click away.

  5. 05

    Ticket or release

    When the customer pays, the booking goes to ticketing; if not, seats are released before the airline cancels them.

  6. 06

    Service until travel

    Queue messages, schedule changes and customer requests are handled from the same booking until the passenger flies.

Key features for reservation staff

  • PNR import and transfer

    Pull in reservations made in the terminal or by another office, and move bookings between agents or branches with history kept.

  • Time-limit work list

    Every held booking sorted by its deadline, so the desk works the most urgent first.

  • Queue handling

    Airline queue messages are matched to bookings and shown as tasks instead of being worked in the terminal one by one.

  • Group and split PNRs

    Groups can be named progressively and individual passengers split into their own record when plans change.

  • Readable fare rules

    Dense rule text organised into conditions an agent can explain to a customer, without altering the filed rule.

  • Terminal in the booking

    Native commands for experienced agents, opened from the reservation and governed by your GDS agreement.

Where reservation teams use it

  • Corporate desks

    Travellers' profiles, policy approvals and reissues for changed meetings handled from one record.

  • Umrah and group departures

    Large group PNRs named as passports arrive, with time limits watched closely during peak season.

  • Sub-agent networks

    Sub-agents book on the consolidator's office through a B2B flight booking system in Pakistan without GDS access of their own.

Implementation process

  1. 01

    Connect your office

    Your GDS credentials are connected so bookings are made and imported on your office.

  2. 02

    Set roles

    Decide who can hold, who can ticket, who can cancel and who can use the terminal.

  3. 03

    Import live bookings

    Open PNRs can be imported so the desk starts with its current workload inside Rezencia.

  4. 04

    Train on the work list

    Staff learn the time-limit and queue views first, since those replace most terminal routines.

Common challenges on a reservation desk

Without a booking system

  • Holds expire because time limits sit in each agent's memory
  • Queues are worked in the terminal, one message at a time
  • New staff need months of command training before they are useful
  • Customer chats and the PNR live in different places

With Rezencia

  • Time limits sit on a shared, sorted work list
  • Queue messages become tasks on the right booking
  • Graphical forms for common changes; terminal for the rest
  • The omnichannel inbox is attached to the booking

How Voraal delivers this

The product behind it.

FAQ

Frequently asked questions

Questions buyers ask about gds booking system.

Ask us anything
  • Can we import PNRs that were created directly in the terminal?

    Yes. A PNR on your office can be imported by record locator and becomes a normal Rezencia booking, with servicing, invoicing and messaging available.

  • How are ticketing time limits tracked?

    The limit is read from the PNR when the booking is created or imported and shown on the booking and the desk's work list. Agents see what is due before the airline cancels it.

  • Do agents still need to know GDS commands?

    Not for routine bookings and changes. Agents who know commands can use the terminal inside the admin; it is a terminal, so those commands must still be learned.

  • Can sub-agents use the booking system without their own GDS access?

    Yes. Sub-agents book through the consolidator's office in their B2B portal. They see the booking and its status; GDS access stays with the consolidator.

  • Are special service requests like wheelchair or meals supported?

    Common service requests and passenger document details are entered through forms and written to the PNR. Less common entries can be made through the terminal.

  • Is every change to a reservation recorded?

    Yes. Changes made in Rezencia are logged against the booking with the user and time, alongside the GDS record.

Let’s build what comes next.

Tell us how your travel business works. We’ll recommend the right products and walk you through them on your own use case.

WhatsApp