When
The client wants the itinerary before or after ticketing, or you need a printed PNR.
Steps
| # | Entry | What it does | Why |
|---|---|---|---|
| 1 | IBD | Displays a plain-text itinerary on screen. | Check what the client will get. |
| 2 | IEP-EMLA | Emails the graphical itinerary to the address in the APE element. | The normal way to send it. |
| 3 | [email protected] | Emails it to a given address. | Another recipient. |
| 4 | IEP/LP GE · IEP/P1-2 · IEP/S3-4 | In German · for passengers 1-2 · segments 3-4. | Language and scope. |
| 5 | IBP-EMLA | Emails the plain-text version. | When a simple text is better. |
| 6 | RIR FREEFLOW TEXT | Adds an itinerary remark printed on the document. | A note for the client (meeting point, reminder). |
| 7 | WRA/RT | Prints the whole PNR on your default printer. | Paper copy for the file. |
Graphic: Products → Issue itinerary → type, passengers, language, Print / Email; or Generate ADTD for the Amadeus Dynamic Travel Document.
Check it worked
Amadeus confirms the send; ask the client to check spam if it does not arrive.
Traps
- An itinerary is not a ticket. Before ticketing it proves nothing but the reservation; after ticketing send the e-ticket receipt too (Sending the e-ticket receipt (ITR) and itinerary to the client).
- Remarks with
RIRare printed for the client — never put internal notes or net prices there. - A client offer your agency writes itself is its own document; this Amadeus itinerary is a separate one.