Page Comparison

The Agilysys Visual One OTA Monitor

The Agilysys Visual One OTA Monitor is essential to chameleon™.

The OTA Monitor is installed by the Agilysys Integrations team, and training in its use is provided by Agilysys.

To manage chameleon™, the Property must have access to the OTA Monitor, and be familiar with how to use it to map booking data, including how to map room types, tariffs, packages and the GROUP tariff.

The OTA Monitor serves two purposes for chameleon™:

1. All reservations that arrive through chameleon™ are logged in the OTA Monitor. When a reservation errors, the OTA monitor logs vital error information essential to troubleshooting to isolate the cause of the error.
   
   
2. Mapping of room types, tariffs, packages and the GROUP tariff is required to pass Segment Codes and Origin Codes into Visual One. If the mapping is not complete, reservations will fail or be incomplete, and are logged with a status of "LOST".
   
   

b4checkin products that require the OTA Monitor: 

• chameleon™ by b4checkin (booking engine)
• Legacy booking engine (b4checkin's original booking engine)
• Tripadvisor’s TripConnect
• Expedia QuickConnect
• GDS (when contracted directly with b4checkin)
• Siteminder interface
  
  

The following articles describe how to map items in the Agilysys Visual One OTA Monitor:

1. Agilysys Visual One Tariffs & OTA Monitor Mapping
   All tariffs that you wish to sell through chameleon™ must be mapped in the OTA Monitor.
   
   
2. Agilysys Visual One Packages & OTA Monitor Mapping
   All packages that you wish to sell through chameleon™ must be mapped in the OTA Monitor.
   All packages associated with group booking IDs must be mapped in the OTA Monitor.
   
   
3. Mapping the GROUP Tariff in the Agilysys Visual One Groups & OTA Monitor for chameleonMapping
   
   The GROUP tariff must be mapped in the OTA Monitor in order to offer group bookings online.
   Properties with tariffs associated with groups must map those tariffs in the OTA Monitor.
   All packages associated with group booking IDs must be mapped in the OTA Monitor.
   
   
4. Mapping a Room Type in the OTA Monitor for chameleon
   
   All room types to be offered through chameleon™ must be mapped in the OTA Monitor.
   
   

Items in the OTA Monitor that b4checkin does NOT use:

• Floor Limits screen (Note: these DO apply to the Siteminder Interface)
• Code Routing screen
• Per Person Surcharges screen
• Group Routing screen
• Hotel Codes screen
• Rate Plans by Room Type screen
• The “description” field on the Rate Plans screen