Sabre Red 360 Guide: What New Agents Need to Know

Sabre Red 360 is the graphical workspace most Sabre-connected agencies use today. It has largely replaced the old "green screen" terminal as the thing agents look at all day, but the cryptic command language is still there, running underneath and available in a terminal pane. This guide covers how the pieces fit together, when to click and when to type, and what a new agent should practise first.

What Sabre Red 360 Actually Is

Red 360 is Sabre's desktop and web-based workspace for travel agencies and independent advisors. You use it to search, price, book and service air, hotel, car and other content that comes through the Sabre GDS. It is a mixed interface: point-and-click screens for the workflows that benefit from being visual, plus cryptic command entry for everything else. Sabre's own developer documentation describes an application you can extend with add-ons called Red Apps, with side panels, a graphical PNR display, seat maps and a terminal-style emulator all living in the same window.

What you see depends on your office. Your agency or host agency decides which panels, apps and content sources are switched on, so two agents using "Red 360" can have noticeably different screens. Treat this guide as the shape of the product, not a screen-by-screen manual.

The Three Layers You Work In

1. Graphical screens. Search forms, results grids, seat maps and graphical itinerary views. These are the easiest way to compare options and the gentlest way to learn.
2. The cryptic terminal. The native Sabre entries (115DECJFKLAX, 01Y2, ER and so on) typed into a command area. It talks to the same system as the screens, so a booking started in one layer can be finished in the other.
3. Red Apps. Add-on tools built by Sabre, third parties or agencies that plug into the workspace, for example custom workflows, profile tools or decision-support tiles. Availability is controlled by your office.

GUI vs Cryptic Commands: Which to Use When

Even with the graphical interface, most experienced agents still reach for cryptic entries for speed and for the functions the screens don't cover neatly. If a job posting says "must know Sabre", it almost always means comfort with the underlying command language, not just clicking through menus. In practice the choice usually looks like this:

This is a rule of thumb from how agents tend to work, not a Sabre recommendation. Plenty of agents do everything on screen, especially for simple domestic trips.

One Booking, Two Ways

Imagine a new agent, Priya, booking one passenger from New York to Los Angeles on 15 December. In the graphical layer she fills in the origin, destination and date, picks a flight from the results grid, enters the traveller's name and contact details in forms, sets the ticketing deadline and saves. Exactly what each form is called varies by version and office.

The same job in the terminal is seven short lines, shown here for illustration only. The line number and class letter come from the live availability screen.

115DECJFKLAX
01Y2
-LOPEZ/MARIA MS
9212-555-0100-H
7TAW10DEC/
6PR
ER

Those seven lines are, in order: availability, sell one seat in Y class from line 2, passenger name, phone, ticketing deadline, received-from (who made the booking) and end-and-redisplay. Priya's host agency may require additional fields before the booking will save. See our command cheat sheet for the Amadeus and Galileo equivalents.

Cryptic Entries Worth Learning First

You don't need hundreds. These get most new agents through a normal day. Formats can vary slightly by office, so confirm against your own training material.

Red Apps and Customisation

The Red Apps layer is what separates Red 360 from a simple terminal. Sabre publishes a development kit for building Red Apps, and its documentation lists things like custom workflow side panels, decision-support tiles on the booking screen and services that fetch and display PNRs. For an agent this mostly means that a larger agency or host may have tools in your window that a solo agent's setup doesn't. If something you expect isn't there, ask your agency's Sabre administrator whether it is enabled for your office rather than assuming Red 360 can't do it.

What's New: Launchpad, Mosaic and AI Tools

Sabre has been busy around Red 360, and three things are worth knowing. All of this sits alongside Red 360, not in place of it.

• Sabre Red Launchpad. Announced in March 2024 as a streamlined booking tool for new and independent consultants, covering basic flight, hotel and car bookings. Sabre described it as an extension of Red 360, and bookings needing complex service can be passed to colleagues working in Red 360.
• Sabre Mosaic. At ITB Berlin in March 2026 Sabre presented Mosaic as its rebuilt, AI-first platform with a new brand identity. Some agency product listings now carry the Mosaic name, so check which name your office uses for the same workspace.
• Agentic APIs and an MCP server. In September 2025 Sabre introduced agentic-ready APIs and a Model Context Protocol server so that agencies and developers can connect their own AI tools to Sabre. This is aimed at developers and larger organisations. It doesn't change what you type on a Tuesday morning.

Reading What Red 360 Produces

Whether you book through the graphical screens or the terminal, the PNR that gets created has the same structure described throughout our guides: passenger lines, numbered flight segments, status codes. Red 360 changes how you create the booking, not what it contains.

1.AHMED/KARIM MR
2 PK 273 Y 20NOV 5 KHIDXB SS1  930A 1130A
3 EK 201 Y 28NOV 6 DXBLHR SS1  830A 1200P

The flight numbers and times above are illustrative. Read a real PNR line by line using our Sabre guide, and look up unfamiliar codes in the status code reference.

Mistakes New Agents Make in Red 360

• Trusting the screen over the record. A tidy graphical view can hide a waitlisted segment or a missing field. Before you tell a client they're booked, display the raw PNR with *R and read the status codes.
• Assuming a booking is saved. It isn't until you have ended the transaction and seen a record locator. If you are interrupted, redisplay and check before closing anything.
• Learning only the GUI. The first time a screen won't do what you need, you're stuck. Two weeks of typing the basic entries pays off for years.
• Copying from the wrong view. If you paste into a converter, copy the plain-text *R display, not text dragged out of a graphical panel. Graphical views can reformat or drop text, which is a common reason a paste doesn't parse cleanly.
• Forgetting your office's rules. Mandatory fields, queue settings and ticketing steps are set by your agency. When an entry that "should work" is rejected, that is usually why.

Getting Comfortable With Red 360

A sensible first month for a new agent, for illustration:

1. Week one: use the graphical screens for everything, but after each booking display the raw PNR with *R and match every screen field to a PNR line.
2. Week two: start typing availability, sell, names, end and retrieve. Keep the cheat sheet beside you.
3. Week three: practise corrections: cancelling a segment, rebuilding from an airline email, using ignore when unsure.
4. Week four: add pricing and fare display, and ask a colleague to review a couple of your PNRs for missing elements.

Use any official Sabre training your host agency provides. Formal training shortens the learning curve far more than working it out alone, and it will cover your office's own rules, which no general guide can.

Converting What You Book

Once a booking is made, turning the raw PNR into something a client can read is a separate step many agents still do by hand. Paste the Sabre text into PNRGenius's free converter and you get a clean itinerary, whichever interface produced the booking. Our Sabre converter guide covers how that works.