I had been calling the other fandango number an...
A Fandango customer review by GetHuman user ~stephanieashiley from November 9th, 2017
Background on ~stephanieashiley's case
GetHuman: ~stephanieashiley - can you tell our other Fandango customers when your case took place?
~stephanieashiley: Sure. It was afternoon, on November 2nd.
GetHuman: Did you reach out to Fandango, and if so, how?
GetHuman: And which of these common Fandango customer issues best describes the reason you wanted to talk to them?
(Shows ~stephanieashiley a list of common Fandango problems)
~stephanieashiley: "Exchange Tickets" was why I was trying to call.
~stephanieashiley's review of Fandango customer service
GetHuman: So how would you sum up your experience for GetHuman's Fandango 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.
~stephanieashiley: I had been calling the other fandango number and they put me on hold for **min with NO ANSWER!! This number works and the response time was fast! the man who helped me was extremely nice and I got my refund!
GetHuman: Let's quantify your experience contacting Fandango. On a scale of 1 to 5, how easy is it go get help on a Fandango problem?
~stephanieashiley: I'd give them a one 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?
~stephanieashiley: I'd give them a one out of five on communication.
GetHuman: And what about Fandango's ability to quickly and effectively address your problem?
~stephanieashiley: For that I would say two out of five.
GetHuman: And finally- any advice for other Fandango customers?
~stephanieashiley: Call them early in the day or late. Don't forget any personal or account information you might need for Fandango to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~stephanieashiley taken from his Fandango customer service problem that occurred on November 2nd, 2017.