After the Universal Record and provider PNR are created, the PNR can be placed on an agency queue by the provider or customer, for quality control, ticketing, or other work as required by the agency business process.
Queuing is typically an agency function; agents typically sign on to a queue to work with PNRs. Queues display as a first in/first out set of PNRs. PNR/BFs can optionally be saved to more than one queue.
Samples: Queue samples can be found here.
The following Queue Management functionality is available to allow agencies or other travel providers to manage queued bookings for all agent-authorized branches:
- Queue Count, which retrieves the number of PNR record locators that exist on each queue for specified Pseudo City Code (PCC).
- On Galileo (1G) and Apollo (1V):
- A PCC can have a maximum of 100 (0-99) Queues.
- Each queue can have a maximum of 100 categories.
- Each category can have a maximum of four Date ranges (D1, D2, D3, D4).
- On Worldspan (1P) depending on provisioning:
Level 1 – 25 Queues
75 categories with four Date Ranges
165 categories without Date Ranges.
Level 2 – 255 Queues
15 categories with four Date Ranges
33 categories without Date Ranges
- Level 3 – 255 Queues
- 75 categories with four Date Ranges
- 165 categories without Date Ranges
- Queue List, which lists the PNR record locators that exist on a specific queue, including either:
- All PNR record locators in the queue.
- PNR record locators for a requested surname (last name) in the queue.
- Queue Agent List, which lists an agent's active PNR record locators for each queue.
- Multiples queues can be open at the same time for a PNR record locator. Previously releases allowed only one queue to be assigned to a PNR.
- Queue Agent List is the only queue functionality that is not available for Worldspan (1P).
- Queue Enter, which signs the customer into a specific queue to work a booking for either:
- A specified Pseudo City Code (PCC).
- A specified PNR record locator in the PCC.
Consolidators can access to Universal Records/PNRs only on specified queues for an agency that they are permitted to emulate. Consolidator Queues are only available for Galileo (1G).
- Queue Next, which allows the customer to keep the current booking on queue, and get the next PNR in the queue.
- Queue Place, which allows the customer to add a specific PNR to a queue in the GDS system for a specific Pseudo City Code.
- Queue Exit, which signs the customer off the Queue they had previously signed into. Does not alter the record.
- Universal Record (UR) Modify while on Queue, which allows the customer to update any component in an existing Universal Record from a queue, and update the UR History with the details of the queue information. The customer can then view the original booking again, get the next PNR in the queue, or exit the queue.
Note: If a customer is on a queue but modifies a PNR using a request other than UR Modify, the Queue Next and Queue Exit functionality are not available. For example, a customer is on a queue and modifies a Hotel segment. Because the hotel update request does not use the UR Modify request, Queue Next/Exit cannot be used. However, if a customer is on a queue and updates a Hotel segment, then performs a task using UR Modify, the queue next/exit option can be used, since the last task performed was a UR Modify request.
Exceptions
Previously, most queue functionality was only available on Galileo (1G) and Apollo (1V). With GDSQueue v35.0 and later, most queue functionality (except Queue Agent List) is available on Worldspan (1P).
ACH does not support queues.
Feedback / Support
