SSRs FOR PASSENGER CONTACT INFORMATION.
Dear Travel Partner, We hope you had a lovely weekend! We thank God and Allah for yet a new month. Below is our weekly tip, SSRS FOR PASSENGER CONTACT INFORMATION. IATA Resolution 830d requires travel agents to actively ask each customer whether they wish to have their contact details provided to airlines for the purposes of contact for operational notifications only. This includes flight cancellations, delays or early departures and irregular operations. The contact details are entered as SSR which includes the mobile phone and/or email address of the passenger. Many airlines use automated notification processes to send flight delay alerts by email or text message directly to the passenger. The following SSRs codes have been created for this purpose: CTCE Passenger contact e-mail address CTCM Passenger contact mobile phone number CTCR Passenger refused to provide contact details It is recommended to add these SSRs in every Booking File when created. Airlines use different communication methods for contacting passengers. These SSRs can also be added to client files and business files How does it work? If only the e-mail is provided, the airline will message using e-mail. If only the mobile phone number is provided, the airline messages using SMS/text message (no phone calls). If both e-mail and mobile are provided, the airline will use e-mail when it is more than 24 hours before departure and use SMS/text message within 24 hours. Note: Some airlines do not yet support these SSRs for passenger contact information. If there is any doubt, please contact the airline. |
![]() |
Passenger name selection is required, even for a single passenger Booking File. The phone number should be entered with no spaces and no special characters. The contact information must be added for each passenger separately; however, the same contact information can be used for more than one passenger. Carrier code YY can be used to send the contact information to all carriers in a Booking File. Preferred language can be included in the SSR using the language codes. Languages supported by carrier may vary. Public site for language codes according to ISO-639-1 When a BF is divided, the relevant SSR items are moved to the new BF. When a name is changed or deleted, all related SSR items are cancelled. The SSRs need to be entered again for the revised name. |
![]() |
![]() |
Note: If more than one email address is provided for one passenger, the airline may select the last CTCE SSR received, assuming it to be the most current. |
![]() |
Kind regards, Travelport |
This Post Has 0 Comments