Service Levels

Preferred Connectivity Service Levels (“SLA”)

May 4, 2020 Update:

We have temporarily revised our service levels to the following:

Direct Connect – all at 20 days (IBS connections have no SLA)
Interfaces – 45 days
SynXis Logins – 5 days
SHU Logins – 10 days
Rate Loading – 10 days
Booking Engine – 10 days for all inquiries
OTA DIRECT CONNECT 

Preferred Hotels and Resorts makes an effort to implement connectivity from SynXis to a PMS, CMS or RMS via one-way, two-way or two-way enhanced interfaces within 45 business days.

SLAs of 10 business days for:

Expedia

Booking.com

Tablet_Hotels

Secret_Escapes

Kiwi_Collection

Splendia

 

SLAs of 20 business days for:

Virgin_Holidays

American_International_Tours_(ATI)

DOTW

Destinations_of_the_World

Island_Destinations

LastMinute

Agoda_Priceline

Hotels_Combined

Getaroom.com

Mr_and_Mrs_Smith

Logitravel

Best_Day_Travel

Tiket.com

i-escape

EET_Global

Traveloka

HRS

GTA_Margin

Cleartrip

Superbreak

Hoterip

 

 

Any OTA that requires use of the CCX functionality has a 30 day SLA, including but not limited to:

Abreu

Ctrip

Egypt_Express

Fincahotels.com_via_CCX

GTA

GTA_Margin

GTAstatic

Hotelbeds

HRS

JacTravel

JumboTours

MetGlobal

NetAffinity

Odigeo

Ostrovok_CCX

Smart_System_Holidays

STC

STglobe

TOMAS-CCX

 

Any OTA that uses the IBS (formerly HBSi) connectivity has NO SLA (GTA, Delta Vacations, Pleasant Holidays, Overseas Travel International, Libgo/Liberty Travel, et al.)

 

Interfaces 

Preferred Hotels and Resorts makes an effort to implement connectivity from SynXis to a PMS, CMS or RMS via one-way, two-way or two-way enhanced interfaces. The expected SLA for any interface is 45 business days.

 

Rate Loading 

Preferred Hotels and Resorts Database Services offers a 2 business day rate loading SLA from March through October and 5 business days from November through February.

 

User IDs 

Request for SynXis User IDs is 3 business days. It is recommended that hoteliers reach their hotel’s Super User to assist in user requests due to the delay in processing requests given to Preferred.

 

Helpful Hints

Jira Portal Access: How to review request status