Tres assigns Trip and Reservation Advisors based on GDS interface activity and optional *SA remarks in the PNR. Accurate advisor assignment ensures proper tracking of booking responsibilities, commissions, and client communication. This article explains how advisors are assigned by default, how to override them using *SA, and how to manage multi-advisor scenarios.
Default Advisor Assignment Logic
Trip Advisor
When a trip is created via interface, Tres assigns the Trip Advisor based on the GDS user who created the PNR.
Reservation Advisor
If the same GDS user also issues the ticket or invoice, their advisor interface ID is assigned to each reservation.
Dual Advisor Scenario
If the PNR is created and ticketed by different GDS users:
- The PNR create agent is assigned as the Trip Advisor
- The ticketing agent is added as a Reservation Advisor to each reservation
This results in two advisors per reservation when booking and ticketing are handled by separate users.
Customizing Advisor Assignment with *SA
The *SA remark allows manual control over advisor assignments. Each GDS uses different formats for entering coded remarks for Tres. See GDS-Specific Examples below for examples.
Add a Reservation Advisor
To add an advisor to reservations without overriding the Trip Advisor:
*SA(advisor interface ID)
- The Trip Advisor remains assigned based on the PNR create agent
- The advisor in the *SA entry is added to each reservation
Example:
*SATM
- TM is added as a Reservation Advisor
- Trip Advisor remains the PNR create agent
Override All Advisor Assignments
To override both Trip and Reservation Advisors:
*SA
*SA(advisor interface ID)
*SA(advisor interface ID)
- The first *SA (without an ID) disables default assignment based on GDS users
- The first advisor ID becomes the Trip Advisor
- All listed advisor IDs are assigned to each reservation
Example:
*SA
*SATM
*SAJH
| Role | Assigned Advisor |
|---|---|
| Trip Advisor | TM |
| Reservation Advisors | TM, JH |
Important:
The *SA override must appear before any advisor ID entries to take effect.
Advisor Assignment Summary
| PNR Entry(s) | Trip Advisor | Reservation Advisor(s) |
|---|---|---|
| (none) | PNR create agent | PNR create agent and ticketing agent |
| *SA(advisor ID) | PNR create agent | PNR create agent and Advisor in *SA entry |
| *SA + *SA(advisor ID) | First advisor in list | All advisors in *SA entries |
GDS-Specific Examples
Each GDS has specific formats for entering coded remarks to Trams. The following examples illustrate how to add an advisor interface ID.
| Amadeus | Sabre | Travelport+ |
|---|---|---|
| RM Example: RM*SATM | 5.S* Example: 5.S*SATM | DI.FT- Example: DI.FT-SATM |
Troubleshooting Advisor Assignment
If advisor assignments aren’t appearing as expected:
- Ensure the *SA override appears before any advisor ID entries
- Verify that all advisor interface IDs are valid and correctly formatted
- Confirm that the PNR was processed through interface with expected GDS user activity
- Check the Trip Import screen to see which advisor IDs were transmitted and applied