Overview of GDS Queue Architecture
A GDS queue is an internal mailbox and task distribution system within Global Distribution Systems such as Amadeus, Sabre, and Travelport. Airlines, automated system robots, and agency consolidators send Passenger Name Records (PNRs) to specific numbered queues to alert travel consultants about critical updates requiring manual intervention or passenger communication.
Queues are structured logically by numerical identifier (e.g., Queue 0, Queue 1, Queue 7, Queue 8, Queue 10) or alphanumeric categories. Each queue serves a dedicated operational purpose, categorizing work items to prevent booking failures, involuntary schedule drops, or unnotified passenger disruptions.
Standard Queue Categories and Functions
• Queue 0 (General Message / Ticketing Time Limit): Often designated for general administrative messages, Ticketing Time Limit (TTL) warnings, or automated cancellations generated by airline inventory revenue management engines.
• Queue 1 (Schedule Changes and Flight Disruptions): Receives PNRs affected by airline timetable alterations, flight cancellations, equipment swaps, or retimed flight legs (often flagged with UN/TK or NO/HK status codes).
• Queue 2 (Confirmations and Waitlist Clearances): Contains bookings where previously waitlisted segments (HL or WL status) have cleared to confirmed status (KL or HK), requiring prompt confirmation to secure the seat.
• Queue 7 or 8 (Ticketing and Automated Reissues): Dedicated to bookings pending electronic ticket issuance, automated re-pricing queues, or failed automated ticket reissues.
• Queue 97/98 (System Reject and Error Queues): Receives PNRs that could not be processed automatically due to syntax errors, invalid frequent flyer numbers, or rejected auxiliary service requests.
Daily Operational Discipline and Servicing Workflows
Travel agencies must establish strict Standard Operating Procedures (SOPs) for queue servicing across shifts:
• Morning sweep: Travel consultants start the business day by checking all active queues, prioritizing Schedule Changes (Queue 1) and Waitlist Confirmations (Queue 2).
• Handling Schedule Changes: The agent must inspect the airline advice code (such as SC, TK, or UN). The agent verifies passenger contact information, presents alternate routing options if involuntary changes occurred, confirms new flight segments, removes inactive/cancelled segments (HX, UN, UC, NO), and updates the passenger's electronic ticket if coupons require revalidation or reissue.
• Managing Waitlist Clearances: When an airline confirms a waitlisted segment, it assigns a strict confirmation time limit. If the consultant fails to acknowledge the KL status and update the segment to HK before the airline deadline, the inventory engine automatically cancels the confirmed seat.
• PNR Clean-up and Queue Movement: Once a consultant finishes processing a PNR, they must remove it from the queue using system-specific commands (such as `QEQ` in Amadeus or `QR` in Sabre) or move it to a follow-up queue (`QS` / `QEP`). Leaving processed records in active queues clogs workflows and causes duplicate servicing.
Operational and Financial Risks of Neglecting Queues
Failing to monitor queues daily introduces serious operational risks:
• Passenger stranding: Passengers arrive at airports unaware of schedule changes or flight cancellations, leading to complaints and compensation liability.
• Ticket auto-cancellation: Expiration of unmonitored Ticketing Time Limits causes automated booking cancellation (HX/XX status), resulting in lost fare classes and higher rebooking costs.
• Agency Debit Memos (ADMs): Failure to remove rejected segments (HX, NO, UC) can cause airlines to issue inventory churn or inactive segment penalty debit memos against the agency's IATA/ARC number.
Key takeaways
• GDS queues are structured communication pipelines between airlines and travel agencies for schedule changes, waitlist clearances, and time limits.
• Daily queue sweeps at opening, midday, and shift handover are vital to prevent passenger disruptions and booking cancellations.
• Immediate removal of inactive status codes (HX, UN, UC, NO) protects agencies against airline ADM penalties for inactive segment holding.
• Proper queue discipline requires clearing every processed PNR from the queue immediately after completing servicing.