Fandango: I never spoke to a customer service rep. I was...
A Fandango customer review by GetHuman user GetHuman-394181 from November 20th, 2017
Background on GetHuman-394181's case
GetHuman: GetHuman-394181 - can you tell our other Fandango customers when your case took place?
GetHuman-394181: Sure. It was morning, on November 11th.
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 GetHuman-394181 a list of common Fandango problems)
GetHuman-394181: "Exchange Tickets" was why I was trying to call.
GetHuman-394181'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.
GetHuman-394181: I never spoke to a customer service rep. I was thrown into an automated survey asking me to rate the customer service I received, and was then disconnected. This happened the *nd time I called, but after waiting ** minutes.
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?
GetHuman-394181: I'd give them a three 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-394181: 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?
GetHuman-394181: For that I would say one out of five.
GetHuman: And finally- any advice for other Fandango customers?
GetHuman-394181: 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 GetHuman-394181 taken from his Fandango customer service problem that occurred on November 11th, 2017.