I have booked a flight to ***an from LHR -HND on *********.*It is a BA code share fligh...

GetHuman-chiyojib's customer service issue with Japan Airlines from April 2018

2 views
 | 
108 similar
 | 
0 following
Help with my Japan Airlines issue
How did GetHuman-chiyojib do it?
Waiting to hear how GetHuman-chiyojib fixed the problem to share with other customers.
I have booked a flight to ***an from LHR -HND on *********.*It is a BA code share flight JL*****I have tired to reserve an aisle seat on medical grounds but BA states they have no control as this is operated by JAL. I have a spine injury which makes me have to move frequently from my seat. It would appear only ** aisle seats remain. I am contious that this would cause other p***engers inconvenience should I end up with a middle seat.*If at all possible could JAl kindly reserve an aisle seat,for this flight.*P***enger: vincent OBrien*JL**** LHR-HND **********Many thanks
I trust that Japan Airlines will make this right and come up with a resolution that is fair.
Help with my Japan Airlines issue
Follow this to see how it gets fixed
Do you have a customer issue as well?
We can help you get Japan Airlines's attention and get better help faster. Tap below to get started.
Having Japan Airlines issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
How would Japan Airlines email you?
This email address isn't valid
Follow this issue
See how GetHuman-chiyojib fixes it.
This email address isn't valid

Japan Airlines

Customer service issue
Reported by GetHuman-chiyojib
Apr 30th, 2018 - 3 mons ago
I have an issue with Japan Airlines too
Fixed
Seen by 2 customers so far
Similar issue to 108 others
0 customers following this
Follow this issue to see how it gets fixed
Items needed
Name on the ticket
Booking reference
Billing address
Email address on the account
Frequent Flyer number (if applicable)
Timeline
GetHuman-chiyojib started working on this issue
Apr 30th 8:27am
GetHuman-chiyojib confirmed the issue is fixed. Hooray!
May 1st 10:26am