GDS Contact Details
Applicable to pure TR on 668 and 618
Email address and Mobile numbers are required for airline to contact agent/passengers.
Refer to the table below for GDS entry formats.
| GDS | OSI format | SSR format |
| Amadeus | OS TR CTCM SIN 6592291111 OS TR CTCE EMAIL..ADDRESS//AGENT.COM | SR CTCM-659229111 SR CTCE-EMAIL..ADDRESS//AGENT.COM |
Sabre/ Abacus/ Infini | 3OST TR CTCM SIN 6592291111 3OSI TR CTCE EMAIL..ADDRESS//AGENT.COM | 3CTCM/659229111-1.1 3CTCE/EMAIL..ADDRESS//AGENT.COM-1.1 |
| Galileo | >SI.TR*CTCM SIN 6592291111 >SI.TR*CTCE EMAIL..ADDRESS//AGENT.COM | >SI.P1/SSRCTCMTRHK1/6592291111 >SI.P1/SSRCTCETRHK1/EMAIL..ADDRESS//AGENT.COM |
| Travelsky | OSI TR CTCM SIN 6592291111/P1 OSI TR CTCE EMAIL..ADDRESS//AGENT.COM/P1 | SSR CTCM TR HK1 6592291111/P1 SSR CTCE TR HK1 EMAIL..ADDRESS//AGENT.COM/P1 |
Rules:
(a) Enter phone format as country dialing code first, then mobile/ cell number with leading zero removed.
E.g.: If mobile number is 92291111 with Singapore country code +65, enter as 6592291111.
(b) Always include city code, where applicable, when indicating phone number.
(c) When entering an email address use // in place of @, and .. in place of _
E.g.: EMAIL..ADDRESS//AGENT.COM = EMAIL_ADDRESS@AGENT.COM
(d) Use the applicable carrier code in the key entry, i.e. TR.
(e) Entries can be passenger-associated (e.g. P1, N1, -1.1).
(f) SSR CTCE format must be used to indicate passenger contact details.
(g) Should passenger wish to opt-out from being contacted, kindly send SSR CTCR with agent contact details in OSI CTCE format.
(h) If contact email is blank, agents must bear responsibility of contacting passengers if schedule changes occur. Airline will not be held responsible.
(i) Recommended: Agent who initially booked the flight should be the only one updating the PNR. Changing IATA organization could cause a possible reprice. Agent should check with the airline to verify no reprice has occurred.
Other enquiries, please direct to
sales@flyscoot.com