Passenger contacts
![](/resource/image/3480890/landscape_ratio16x9/1000/563/6581e7d0b9cede7dad62915900b25d28/DACC691B5AF87EA388CD12EEC2FD34B7/finnair-helsinki-airport-terminal-man-and-boy-walking-v3.jpg)
![](/resource/image/3480890/landscape_ratio3x2/600/400/701322f792541238dc632faa837d31a6/269D4C5D329336783BE3E18A34CB3E66/finnair-helsinki-airport-terminal-man-and-boy-walking-v3.jpg)
According to IATA Resolution 830d, it is necessary to have contact details in case of non-commercial purposes e.g., inform passenger about flight delays or cancellations.
Passenger contact information is used by different automation systems to provide customers with relevant information. This includes sending of documents (ticket, EMD, itinerary) and disruption notices regarding customers' booking. Elements can be booking or customer specific and it is important to specify when a contact element should be personal and PNR wide.
Instructions for NDC bookings
Passenger contact details are required to be entered at the time of the booking. For the time being, contact details cannot be added or changed after booking is created via NDC channels. Passenger contact details can be updated at any time via Manage booking or by contacting Agent Help Desk.
Instructions for Edifact bookings
Passenger contact details must be added as SR CTC according to the following examples. Contact details can be inserted additionally for example on AP lines.
Mobile number as SR CTCM element
E-mail address as SR CTCE element
*It is possible to define preferred language after mobile number or email. However, this is optional extra information.
In case customer refuses to give any contact details: use SR CTCR element
For example in Amadeus: SRCTCR-REFUSED/P1
For specific Edifact entries in GDS, please contact your own GDS Help Desk.