Fandango: bought * $** gift cards to be emailed, was char...
A Fandango customer review by GetHuman user ~steve fitz from November 20th, 2017
Background on ~steve fitz's case
GetHuman: ~steve fitz - can you tell our other Fandango customers when your case took place?
~steve fitz: Yeah. It was morning, on November 13th.
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 ~steve fitz a list of common Fandango problems)
~steve fitz: "Refund a Charge" was why I was trying to call.
~steve fitz'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.
~steve fitz: bought * $** gift cards to be emailed, was charged but gifts never emailed. they failed to respond to my help line email only fixing after I did live chat and will not offer any comp. Looks like they purposely tried to do this. live chat knew right away their system was broke the day I ordered.
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?
~steve fitz: 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?
~steve fitz: I'd give them a two out of five on communication.
GetHuman: And what about Fandango's ability to quickly and effectively address your problem?
~steve fitz: For that I would say one out of five.
GetHuman: And finally- any advice for other Fandango customers?
~steve fitz: 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 ~steve fitz taken from his Fandango customer service problem that occurred on November 13th, 2017.