Disney Movie Club: She had a hard time understanding me but otherw...
A Disney Movie Club customer review by GetHuman user GetHuman-256292 from November 27th, 2017
Background on GetHuman-256292's case
GetHuman: GetHuman-256292 - can you tell our other Disney Movie Club customers when your case took place?
GetHuman-256292: Yeah. It was evening, on November 22nd.
GetHuman: Did you reach out to Disney Movie Club, and if so, how?
GetHuman: And which of these common Disney Movie Club customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-256292 a list of common Disney Movie Club problems)
GetHuman-256292: "Return an Order" was why I was trying to call.
GetHuman-256292's review of Disney Movie Club customer service
GetHuman: So how would you sum up your experience for GetHuman's Disney Movie Club 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-256292: She had a hard time understanding me but otherwise quick and painless interaction with the Disney Movie Club.
GetHuman: Let's quantify your experience contacting Disney Movie Club. On a scale of 1 to 5, how easy is it go get help on a Disney Movie Club problem?
GetHuman-256292: I'd give them a five 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-256292: I'd give them a five out of five on communication.
GetHuman: And what about Disney Movie Club's ability to quickly and effectively address your problem?
GetHuman-256292: For that I would say five out of five.
GetHuman: And finally- any advice for other Disney Movie Club customers?
GetHuman-256292: Call them early in the day or late. Don't forget any personal or account information you might need for Disney Movie Club to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-256292 taken from his Disney Movie Club customer service problem that occurred on November 22nd, 2017.