Disneyland Resort: wow, very quick pick up. Phone tree was easy. T...
A Disneyland Resort customer review by GetHuman user ~David-in-SLO from November 27th, 2017
Background on ~David-in-SLO's case
GetHuman: ~David-in-SLO - can you tell our other Disneyland Resort customers when your case took place?
~David-in-SLO: Yeah. It was morning, on November 22nd.
GetHuman: Did you reach out to Disneyland Resort, and if so, how?
GetHuman: And which of these common Disneyland Resort customer issues best describes the reason you wanted to talk to them?
(Shows ~David-in-SLO a list of common Disneyland Resort problems)
~David-in-SLO: "Overcharge/Strange charge" was why I was trying to call.
~David-in-SLO's review of Disneyland Resort customer service
GetHuman: So how would you sum up your experience for GetHuman's Disneyland Resort 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.
~David-in-SLO: wow, very quick pick up. Phone tree was easy. Think I had to hit two numbers ... and had a less than * minute time on hold. Thanks, Disneyland.
GetHuman: Let's quantify your experience contacting Disneyland Resort. On a scale of 1 to 5, how easy is it go get help on a Disneyland Resort problem?
~David-in-SLO: 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?
~David-in-SLO: I'd give them a four out of five on communication.
GetHuman: And what about Disneyland Resort's ability to quickly and effectively address your problem?
~David-in-SLO: For that I would say three out of five.
GetHuman: And finally- any advice for other Disneyland Resort customers?
~David-in-SLO: Call them early in the day or late. Don't forget any personal or account information you might need for Disneyland Resort to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~David-in-SLO taken from his Disneyland Resort customer service problem that occurred on November 22nd, 2017.