Accessing a rate in native GDS
If a travel agent is experiencing issues with accessing a rate, check the travel agent has:
Searched for the rate in their native GDS (example: Amadeus, Galileo, Sabre or Worldspan).
Provided the correct Pseudo City Code (PCC).
Updated their HST tables if using Sabre GDS, to link SiteMinder's Rate Access Code (RAC) to their RAC if the agent uses a different RAC.
Searched using multiple dates.
Selected a one night stay in search criteria.
If the travel agent is still experiencing issues, please raise a case and provide the following information so we can investigate further for you:
The type of GDS the agency uses (example: Amadeus, Galileo, Sabre or Worldspan).
The booking dates requested.
A screenshot of their search results.
Indicate if the agency uses an online booking tool or searches directly in the GDS.
Accessing a rate via Online Booking Tools (OBT)
If the travel agent or company is experiencing issues with accessing rates via their OBT, please ask the agent to check the native GDS first. If the rate is available in the GDS, then the issue is with the OBT.
If the rate is not available in the OBT, then the travel agent will need to contact their OBT technical support team to investigate.
Below are the recommendations to the travel agents for the following OBTs:
Concur - There should be a designated person, identified as the Concur Administrator within the travel agency, TMC or corporate account that uses the Concur OBT, who will have access to configuration settings or will be authorised to contact Concur directly to resolve the rate issue.
Serko - The travel agent/TMC will need to check with their technical support team to ensure that the correct Rate Access Code has been loaded within the Hotel Policy section in Serko.