Fandango: Was charged three times for a movie I already p...
A Fandango customer review by GetHuman user ~Very Angry from November 7th, 2017
Background on ~Very Angry's case
GetHuman: ~Very Angry - can you tell our other Fandango customers when your case took place?
~Very Angry: Yes. It was afternoon, on November 1st.
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 ~Very Angry a list of common Fandango problems)
~Very Angry: "Payment Problem" was why I was trying to call.
~Very Angry'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.
~Very Angry: Was charged three times for a movie I already paid for once.I checked my account and noticed I had been charged three times in a row so it was not an accident.I have been on hold for thirty minutes now and want FANDANGO to know they have ruined my daughters birthday by this.These ppl are rude!!!
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?
~Very Angry: 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?
~Very Angry: I'd give them a three out of five on communication.
GetHuman: And what about Fandango's ability to quickly and effectively address your problem?
~Very Angry: For that I would say four out of five.
GetHuman: And finally- any advice for other Fandango customers?
~Very Angry: 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 ~Very Angry taken from his Fandango customer service problem that occurred on November 1st, 2017.