British Airways: Regular number reached a call center in India t...
A British Airways customer review by GetHuman user GetHuman-107291 from November 15th, 2017
Background on GetHuman-107291's case
GetHuman: GetHuman-107291 - can you tell our other British Airways customers when your case took place?
GetHuman-107291: Sure. It was middle of the night, on November 11th.
GetHuman: Did you reach out to British Airways, and if so, how?
GetHuman: And which of these common British Airways customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-107291 a list of common British Airways problems)
GetHuman-107291: "Cancel or change flight" was why I was trying to call.
GetHuman-107291's review of British Airways customer service
GetHuman: So how would you sum up your experience for GetHuman's British Airways customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
GetHuman-107291: Regular number reached a call center in India that did not know where British Airways flew from! This * much more helpful
GetHuman: Let's quantify your experience contacting British Airways. On a scale of 1 to 5, how easy is it go get help on a British Airways problem?
GetHuman-107291: I'd give them a five out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
GetHuman-107291: I'd give them a two out of five on communication.
GetHuman: And what about British Airways's ability to quickly and effectively address your problem?
GetHuman-107291: For that I would say one out of five.
GetHuman: And finally- any advice for other British Airways customers?
GetHuman-107291: Call them early in the day or late. Don't forget any personal or account information you might need for British Airways to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-107291 taken from his British Airways customer service problem that occurred on November 11th, 2017.