When
Use this card when the airline needs data that has no short programmatic form in Galileo: the traveller's own phone and email, an emergency contact, a frequent flyer number that is too long, group fare details.
How a manual SSR is built
SI. + passenger (P1/, optional) + SSR + four-letter code + airline (YY = all airlines in the file) + HK1 + / + the data.
| Code | What it carries |
|---|---|
CTCM · CTCE | traveller's mobile · email, for disruption messages |
CTCR | the traveller refused to give contact data |
PCTC | emergency contact person |
DOCS · DOCO · DOCA | passport, visa / redress / known traveller, address — see Passport data (APIS / Secure Flight) with SSR DOCS |
FOID | form of identification — see Form of identification (FOID) for e-tickets |
FQTV | frequent flyer number when M. is too short |
GRPF | group fare details |
CLID | corporate client identifier, one per airline per booking |
Steps
| # | Entry | What it does | Why |
|---|---|---|---|
| 1 | SI.P1/SSRCTCMYYHK1/38641123456 | Traveller 1's mobile to all airlines. | Airlines contact the traveller directly about changes. |
| 2 | SI.P1/SSRCTCEYYHK1/ANA.NOVAK//EXAMPLE.COM | Traveller 1's email (// for @, -- for underscore). | Same reason, by email. |
| 3 | SI.P2/SSRCTCRYYHK1/PASSENGER DECLINED | Records that traveller 2 gave no contact. | Text after the last slash is free. |
| 4 | SI.SSRPCTCYYHK1/MARKO KOVAC/SI 386 41 765432-NOVAK/ANAMRS. HUSBAND | Emergency contact (name, country, phone) for traveller NOVAK/ANA; the relationship follows the full stop. | Some airlines ask for it. |
| 5 | SI.SSRFQTVLHHK1/LH992000123456789-NOVAK/ANAMRS | A loyalty number for LH that does not fit in M.. | Fallback for long numbers. |
| 6 | *SI | Shows all service information. | Check codes, airline and text. |
| 7 | SI.4@ · SI.4@XK | Cancels item 4 with a message to the airline · removes it silently. | Wrong data must be removed before adding the right one. |
In Smartpoint: special services script → Special Service Request.
Check it worked
*SI lists the manual SSR with its code, airline (or YY), status and text.
Traps
- A manual SSR cannot be changed — only cancelled and entered again.
- Manual SSRs belong to the booking file, not to a flight segment. Programmatic ones (meals, wheelchairs) are tied to segments.
YYsends to every airline in the file. Put a carrier code instead to send to one airline only.- Data for a lap infant goes on the adult's name.
- Only one
CLIDper airline per booking; remove duplicates withXK. - Slashes are positions: leaving one out shifts every field after it.