Walt Disney World: They still put you to the recording. I wanted t...
A Walt Disney World customer review by GetHuman user GetHuman-229569 from November 26th, 2017
Background on GetHuman-229569's case
GetHuman: GetHuman-229569 - can you tell our other Walt Disney World customers when your case took place?
GetHuman-229569: Yes. It was afternoon, on November 24th.
GetHuman: Did you reach out to Walt Disney World, and if so, how?
GetHuman: And which of these common Walt Disney World customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-229569 a list of common Walt Disney World problems)
GetHuman-229569: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-229569's review of Walt Disney World customer service
GetHuman: So how would you sum up your experience for GetHuman's Walt Disney World 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-229569: They still put you to the recording. I wanted to talk to a person a recording would not help me!!!!!
GetHuman: Let's quantify your experience contacting Walt Disney World. On a scale of 1 to 5, how easy is it go get help on a Walt Disney World problem?
GetHuman-229569: 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-229569: I'd give them a five out of five on communication.
GetHuman: And what about Walt Disney World's ability to quickly and effectively address your problem?
GetHuman-229569: For that I would say four out of five.
GetHuman: And finally- any advice for other Walt Disney World customers?
GetHuman-229569: Call them early in the day or late. Don't forget any personal or account information you might need for Walt Disney World to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-229569 taken from his Walt Disney World customer service problem that occurred on November 24th, 2017.