Called Aeroplan two times. Rude, long waits, an...
A Aeroplan customer review by GetHuman user ~Unhappy customer from November 25th, 2017
Background on ~Unhappy customer's case
GetHuman: ~Unhappy customer - can you tell our other Aeroplan customers when your case took place?
~Unhappy customer: Yes. It was afternoon, on November 17th.
GetHuman: Did you reach out to Aeroplan, and if so, how?
GetHuman: And which of these common Aeroplan customer issues best describes the reason you wanted to talk to them?
(Shows ~Unhappy customer a list of common Aeroplan problems)
~Unhappy customer: "Overcharge on Account" was why I was trying to call.
~Unhappy customer's review of Aeroplan customer service
GetHuman: So how would you sum up your experience for GetHuman's Aeroplan 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.
~Unhappy customer: Called Aeroplan two times. Rude, long waits, and ghastly attitudes. Horrible service both times. Really considering switching out of this program and will be convincing the rest of my family & friends to do the same.
GetHuman: Let's quantify your experience contacting Aeroplan. On a scale of 1 to 5, how easy is it go get help on a Aeroplan problem?
~Unhappy customer: I'd give them a two 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?
~Unhappy customer: I'd give them a one out of five on communication.
GetHuman: And what about Aeroplan's ability to quickly and effectively address your problem?
~Unhappy customer: For that I would say one out of five.
GetHuman: And finally- any advice for other Aeroplan customers?
~Unhappy customer: Call them early in the day or late. Don't forget any personal or account information you might need for Aeroplan to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Unhappy customer taken from his Aeroplan customer service problem that occurred on November 17th, 2017.