Agree.
My only concern is if the ticket becomes ‘unticketed’ once they see the miss connect… which could jeopardise the MH sectors as they will auto cancel. However… not sure if that would trigger in this case?
This was my concern too.
I called (3xHUACA until reaching HBA) and asked about a dozen very specific questions about reticketing, revalidation etc including that it is MNL point of origin and ticketed by MNL office.
I also outlined that the MH flights had dropped three times previously due to partner changes and that on the most recent occasion the whole booking was handed over to <name> who is the OWA guru in HBA and was rebuilt from the start.
Agent could see history in the notes and commented on what a nightmare it had been.
She then advised that because this change was a QF flight they could select alternatives and “force reissue” without affecting any of the partner flights.
I pressed further on whether this required reticketing and the agent advised that yes it would, but that this could be done by the “force reissue” without affecting the partner flights.
She also offered the usual assurance that she’d keep an eye on it and the new tickets would issue “well within 2 hours and likely less than an hour”.
So apprehensively I proceeded:
Outcome was a PDF with new flight details but no ticket numbers within about 15min of the call ending.
I then checked the MH app and the new ticket numbers were showing.
Couldn’t cross-check on RJ because it had gone tech.
Amadeus issued text-only itinerary with new ticket numbers landed about three hours after the call.
As best I can tell without real-time Amadeus access it’s all worked fine.
Here’s hoping…
