Originally Posted by
Often1
Stop.
This entire problem is caused by OP not waiting for CX to follow through with BA as it offered to do.
The ticket now has an "illegal" connection at LHR and is invalid. It is caused by BA, but as CX is the ticketing carrier, it is for CX to fix the problem. In order to do so, CX must contact BA. This is a manual process accomplished throw the OW liaison operation at CX and then BA. It may take several days. There is no guarantee that it will suceed.
But, OP did not wait. He started making other calls and that has now caused him problems because he was "disappointed" that he would have to wait. As the travel is not until next May, he should simply calm down and wait.
OP - Call CX back and see if you can get CX to start the process all over again. Ask CX to contact BA on your behalf and ask for space on the flight you want and for CX to call you back when it hears back. If CX is able to get authority, you will have new tickets and all will be well. If it is not, you will have to take one of the other options.
Do not start calling other places while this process is pending. That is how ticket problems are created.
Given the generally poor quality of CX phone agents these days, I'm skeptical that this contacting the liaison desk stuff is really necessary in this case no matter what the agent said. CX already is aware that BA has caused the misconnect, since OP received a communication from CX telling him/her to call CX to resolve the matter. This is not an instance where a neurotic traveler caught a schedule change before the new data had filtered through to the ticketing carrier. What more permission is CX supposed to receive from BA to resolve this?
The nub of the problem is that CX for whatever reason is anxious to stick to whatever POS restrictions it has placed on the OP's I fare for CX251. Unfortunately, if OP can't get them to bend on that, the options will be the earlier flight with the overnight or losing half a day at the final destination, or a refund.