Nintendo: Called them numerous times for a system transfe...
A Nintendo customer review by GetHuman user ~BetaLeaf from November 26th, 2017
Background on ~BetaLeaf's case
GetHuman: ~BetaLeaf - can you tell our other Nintendo customers when your case took place?
~BetaLeaf: Yup. It was middle of the night, on November 16th.
GetHuman: Did you reach out to Nintendo, and if so, how?
GetHuman: And which of these common Nintendo customer issues best describes the reason you wanted to talk to them?
(Shows ~BetaLeaf a list of common Nintendo problems)
~BetaLeaf: "Update Account Info" was why I was trying to call.
~BetaLeaf's review of Nintendo customer service
GetHuman: So how would you sum up your experience for GetHuman's Nintendo 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.
~BetaLeaf: Called them numerous times for a system transfer and their robot continuously hangs up on me. Their robot tells me to contact them via their online chat and I proceed to do so only to be told I have to call them. I just want the games I already paid for on my system. Still never got a human on the phone.
GetHuman: Let's quantify your experience contacting Nintendo. On a scale of 1 to 5, how easy is it go get help on a Nintendo problem?
~BetaLeaf: 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?
~BetaLeaf: I'd give them a five out of five on communication.
GetHuman: And what about Nintendo's ability to quickly and effectively address your problem?
~BetaLeaf: For that I would say five out of five.
GetHuman: And finally- any advice for other Nintendo customers?
~BetaLeaf: Call them early in the day or late. Don't forget any personal or account information you might need for Nintendo to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~BetaLeaf taken from his Nintendo customer service problem that occurred on November 16th, 2017.