When
Use this card to send a free-text question or request to an airline from inside a Galileo booking file, and to read the airline's answer.
Steps
| # | Entry | What it does | Why |
|---|---|---|---|
| 1 | V.AJU*PLEASE ADVISE PRICE FOR PET IN CABIN | Sends a message to airline JU (A = airline, then its code). | A question no SSR code covers. |
| 2 | ER | Ends the transaction. | The remark goes out when you end. |
| 3 | *VR | Shows all vendor remarks, in and out. | Look for the answer later. |
| 4 | *VI · *VO | Only incoming · only outgoing remarks. | Separate the airline's reply from your question. |
| 5 | V.2@AJU*NEW TEXT · V.2@ | Changes · deletes remark 2. | A change works only in the transaction where you wrote it. |
| 6 | RL.JU*M4R8TZ | Stores airline JU's own locator M4R8TZ. | For passive segments booked outside Galileo. |
| 7 | *VL | Shows the airline locators. | The reference to give the airline on the phone. |
Check it worked
*VO shows your remark; when the airline answers, *VI shows its reply. *HVR shows the vendor remark history, including deleted ones.
Traps
- The answer comes when the airline sends it. Look at
*VIagain later and keep an eye on your queues (Work a queue — sign in, act, remove, sign out). - Use the right channel: a request with a code (meal, wheelchair, pet in cabin
PETC) goes as an SSR, plain information as an OSI (OSI — other service information for the airline). The vendor remark is for real questions. - Up to 180 characters per remark and 99 remarks per file.
- After dividing a booking file, if no new airline locator appears, send a vendor remark asking the airline to action the divide and send the new locator (Divide a booking file (take travellers out)).
- Write in plain airline English, short and in capitals; avoid
+and@, which Galileo reads as entry signs.