Согласно последним усовершенствованиям системы, туристические агенты начнут получать автоматические уведомления от RJ, напоминающие им, что они должны запрашивать у своих пассажиров правильный и доступный телефон и электронную почту, используя элементы SSR CTCM и CTCE, соответствующие резолюции IATA 830d, и вставлять их в PNR после получения согласия пассажира в соответствии с любыми директивами и правилами по защите данных.
В случае отказа пассажира предоставить свои контактные данные, агент должен использовать в PNR правильные элементы SSR CTCR согласно резолюции 830d IATA, чтобы сообщить об этом RJ, и должен убедиться, что пассажиры знают, что они не могут получать информацию от RJ, связанную с изменениями в расписании, задержками или отменами рейсов.
В случае, если контактные SSR не были добавлены, добавлены с неверной информацией или защищены/скрыты, турагент будет нести ответственность за несоблюдение политики бронирования и резервирования RJ и будет нести ответственность за информирование пассажира об изменениях в расписании, задержках или отменах рейсов. ====================================
Dear all,
Good day,
According to latest system enhancements , travel agents will start receiving automatic notifications from RJ reminding them that they shall ask their passengers for the correct and reachable telephone & email using IATA correct SSR CTCM & CTCE elements- as per IATA resolution 830d- and insert them in the PNR after passenger consent is obtained in compliance with any data protection directives or regulations.
In case of passenger refusal to provide their contact details , the agent shall use the IATA correct SSR CTCR- as per IATA resolution 830d- in the PNR to communicate this to RJ, and shall insure that the passengers are aware that they may not receive information from RJ related to schedule changes, flight delays or cancelations.
In case the contact SSRs were not added, added with incorrect information, or secured/concealed , travel agent will be liable for none compliance with RJ reservation & booking policy, and will be responsible of informing the passenger of schedule changes, flight delays or cancelations.
Please circulate this to all agents and offices under your area.
Below is the format of the SSR CTCM/CTCE/CTCR per GDS. If further details about the entries are needed please advise the agents to contact their GDS local offices:
- Amadeus GDS
Passenger’s mobile number: SRCTCM-0060123456789
Passenger’s mobile number with passenger association: SRCTCM-60123456789/P2 (only numeric)
Passenger’s email address: SRCTCE-TRAINING..MY//AMADEUS.COM
Passenger’s email address with passenger association: SRCTCE-TRAINING..MY//AMADEUS.COM/P2
To register that the passenger refuses to provide contact: SR CTCR-PAX REFUSED TO PROVIDE CTC
- Note, you must use:
“..” (double dot) in place of “_” (underscore)
“//” (double slash) in place of “@” (ampersand)
“./” (dot slash) in place “-” (dash)
- Sabre GDS
3CTCM(Segment)/(Phone Number)-(Name Association)
Add a contact mobile/cell phone number to a specific segment for the airline to use in case of irregular operations (IROP).
EXAMPLE: 3CTCM2/1111111111-1.1
3CTCE/(email address)/(language code)-(Name Association)
Add a contact email to all segments and a name field for the airline to use in case of irregular operations (IROP).
EXAMPLE: 3CTCE/TIM.JONES//AOL.COM/EN-1.2
3CTCR(segment)/(free text)-(Name Association)
Add that passenger refused to provide IROP emergency contact with segment select, for any airline except American Airlines.
EXAMPLE: 3CTCR2/REFUSED IROP CONTACT-1.1
- Things to Know
How do I include "@" in the e-mail added in the emergency contact information (3CTCE)? | Use // in place of the @ sign in the e-mail address. |
How do I include an underscore "_" in the e-mail address in the emergency contact information (3CTCE)? | Use .. in place of the _ in the email address. |
How do I include a dash "-" in the e-mail address in the emergency contact information (3CTCE)? | Use ./ in place of the - in the email address. |
- Travelport GDSs
SI.RJ*CTCM 00962792345678
SI.RJ*CTCE tamer.ali//rj.com
SI.P1/SSRCTCRYYHK1/PASSENGER REFUSED TO PROVIDE INFORMATION
- Travelsky GDS
SSR CTCM RJ HK1 1234567890/P1
SSR CTCE RJ HK1 TEST.TEST//TRAVELSKY.COM/P1
*SSR CTCR is not available on Travelsky GDS
