Changing a Passenger on a booking is only allowed if the booking is outside 70 days from the departure date.
Any requests inside 70 days, there will be no changes and CS should pushback.
If the customer insists, escalate to MEL CS.
update as of 14/04/2025
1. CS should NOT process a passenger name change unless payment has been made.
2. For Allotment Bookings (regardless of flight scenario / more than 120 days prior to departure)
After payment, CS can update the passenger name directly in Perseus
For Allotment Bookings (regardless of flight scenario / 71-119 days prior to departure)
After payment, CS can update the passenger name directly in Perseus
3. For 3rd Party/Combination Bookings (No Flights Held or Issued, more than 120 days prior to departure):
IV Fee: no IV Fee
Action: Raise a task to Ops using the snippet: ‘Name Change - Third Party Ops’.
For 3rd Party/Combination Bookings (Flights Held or Issued, more than 120 days prior to departure):
IV Fee: no IV Fee
Action: Raise a task to Ops using the snippet: ‘Name Change - Third Party Ops’.
Action: raise a task to Flights Team for airline cancellation fee (if issued) + new full fare for ticket
4. For 3rd Party/Combination Bookings (No Flights Held or Issued, 71-119 days prior to departure):
IV Fee: $75 per person
+ supplier fees (raise task to Ops using snippet: ‘Name Change - Third party Ops’)
Actions:
Raise a task to Ops using the snippet: ‘Name Change - Third Party Ops’.
For 3rd Party/Combination Bookings (Flights Held or Issued, 71-119 days prior to departure):
IV Fee: no IV Fee
Action: Raise a task to Ops using the snippet: ‘Name Change - Third Party Ops’.
Action: raise a task to Flights Team for airline cancellation fee (if issued) + new full fare for ticket
5. Requests can only be made if the departure is more than 70 days away.
If within 70 days, CS should push back the request.
If the customer insists, escalate to MEL CS.
Keywords: passenger change, passenger swap, name replacement, booking passenger change, pax update