GDS automation — the ticket records itself
The slowest and least reliable part of a ticketing desk is a person retyping what the GDS already knows. A desktop plugin watches the terminal and records each ticket as it is issued, so the data in the system is the data on the screen.
How the capture works
The plugin sits inside Travelport Smartpoint and reads the response screens as the agent works. When a ticket is issued or a booking is Q-shared, the record — passenger, ticket number, PNR, airline, sectors, dates and the filed fare with its taxes — is sent to the agency's account within seconds.
- Galileo (Travelport Smartpoint) and Sabre
- Q-share captured on the queue confirmation, with the exact locator
- Filed fare and full tax breakdown, not just a total
What it refuses to guess
A captured fare has to be visible on the screen it came from. If a figure cannot be found in the captured text it is flagged for a human rather than filled in with something plausible — a missing fare is obvious, an invented one is not.
From capture to invoice
A captured ticket lands in a pending queue. Staff choose the client and the sale price; the vendor, the cost, the invoice and the client's due follow automatically, and the documents go out on WhatsApp.
Questions agencies ask
- Does the plugin change how agents use the GDS?
- No. Agents issue and Q-share exactly as before. The plugin only reads what the terminal shows.
- What if the fare is displayed in a separate window?
- The plugin looks beyond the active terminal for the fare screen. Where it genuinely cannot read one, the ticket is captured without the fare and marked for review rather than being given a guessed figure.
- Is a separate installation needed on each PC?
- Yes — one small plugin per ticketing PC, unlocked with a single-use key issued from the admin panel.
Related
See it with your own tickets
Start a free trial — no credit card, set up in minutes.
Try Agency Automation BD free