Moviefone: Been on hold for over * hours then was disconne...
A Moviefone customer review by GetHuman user GetHuman-255575 from November 26th, 2017
Background on GetHuman-255575's case
GetHuman: GetHuman-255575 - can you tell our other Moviefone customers when your case took place?
GetHuman-255575: Yes I can. It was evening, on November 17th.
GetHuman: Did you reach out to Moviefone, and if so, how?
GetHuman: And which of these common Moviefone customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-255575 a list of common Moviefone problems)
GetHuman-255575: "None of those really matches why I wanted to contact Moviefone that day." was why I was trying to contact.
GetHuman-255575's review of Moviefone customer service
GetHuman: So how would you sum up your experience for GetHuman's Moviefone 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-255575: Been on hold for over * hours then was disconnected. Trying to get a refund on a ticket that I bought for wrong date. Please call me ***-***-****
GetHuman: Let's quantify your experience contacting Moviefone. On a scale of 1 to 5, how easy is it go get help on a Moviefone problem?
GetHuman-255575: 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?
GetHuman-255575: I'd give them a one out of five on communication.
GetHuman: And what about Moviefone's ability to quickly and effectively address your problem?
GetHuman-255575: For that I would say three out of five.
GetHuman: And finally- any advice for other Moviefone customers?
GetHuman-255575: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Moviefone to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-255575 taken from his Moviefone customer service problem that occurred on November 17th, 2017.