V1213
Member
- Joined
- Feb 22, 2011
- Posts
- 191
- Qantas
- LT Gold
- Oneworld
- Sapphire
Hi all,
I'm having a hard time getting Qantas to credit my account for a Finnair code share flight and I'm wondering if anyone else has had similar experiences where Qantas virtually refuse to credit?
The flight in question is AY4063 (YUL-JFK), which is a code share of AA3952.
After I took this flight it looked like the system tried to automatically credit to my account:
As such I sent an email to the frequent flyer team with my boarding pass and e-ticket and requested it be credited manually.
Unfortunately the first response from Qantas was:
I then replied confirming that the flight was purchased as a revenue [non-industry] fare (I had already attached the e-ticket demonstrating this) and that the flight was a regularly-scheduled code share, not a charter.
The next response was:
Clearly Qantas doesn't believe that AY4063 is not a charter flight. I note that when I use the online points earning calculator, Finnair is not an airline that it is aware of for earning points on YUL-JFK flights - just AA and QF appear.
While it is understandable that Qantas is going to have some holes in their database for somewhat obscure city pairs like this, I'm disappointed that they want me to do the leg work and harass Finnair about this. I would've expected Qantas to contact Finnair themselves to verify this, as it would appear Qantas are the ones with the incomplete data set and lack of staff empowerment to deal with it.
Has anyone else had to chase up partner airlines to provide Qantas with confirmation of the status of their flights?
Is it just me that thinks that Qantas has made this unnecessarily complicated?
Keen to hear your thoughts!
Thanks,
Tom
I'm having a hard time getting Qantas to credit my account for a Finnair code share flight and I'm wondering if anyone else has had similar experiences where Qantas virtually refuse to credit?
The flight in question is AY4063 (YUL-JFK), which is a code share of AA3952.
After I took this flight it looked like the system tried to automatically credit to my account:
However, the points and status columns for this entry were both:AY 4063 FLEXIBLE ECONOMY 13JAN18 YUL/JFK
As such I sent an email to the frequent flyer team with my boarding pass and e-ticket and requested it be credited manually.
Unfortunately the first response from Qantas was:
I'm unable to credit your account with Qantas Points for your travel on AY4063 with Finnair, as Charter flights or Industry fares aren't eligible for earning. Points for travel on Classic Flight Rewards are also ineligible for earning.
I then replied confirming that the flight was purchased as a revenue [non-industry] fare (I had already attached the e-ticket demonstrating this) and that the flight was a regularly-scheduled code share, not a charter.
The next response was:
For us to credit the points appropriately, please send a request to Finnair confirming that the flight was not a chartered flight and should be eligible to earn points. The confirmation from them should include the following:
- Flight number
- Date of travel
- Origin and destination
Once we have this letter, we'll be happy to credit your membership as soon as possible.
Clearly Qantas doesn't believe that AY4063 is not a charter flight. I note that when I use the online points earning calculator, Finnair is not an airline that it is aware of for earning points on YUL-JFK flights - just AA and QF appear.
While it is understandable that Qantas is going to have some holes in their database for somewhat obscure city pairs like this, I'm disappointed that they want me to do the leg work and harass Finnair about this. I would've expected Qantas to contact Finnair themselves to verify this, as it would appear Qantas are the ones with the incomplete data set and lack of staff empowerment to deal with it.
Has anyone else had to chase up partner airlines to provide Qantas with confirmation of the status of their flights?
Is it just me that thinks that Qantas has made this unnecessarily complicated?
Keen to hear your thoughts!
Thanks,
Tom