GameStop.com: i've called a number of times, and waited for o...
A GameStop.com customer review by GetHuman user ~embalmer138 from November 25th, 2017
Background on ~embalmer138's case
GetHuman: ~embalmer138 - can you tell our other GameStop.com customers when your case took place?
~embalmer138: Yes I can. It was middle of the night, on November 23rd.
GetHuman: Did you reach out to GameStop.com, and if so, how?
GetHuman: And which of these common GameStop.com customer issues best describes the reason you wanted to talk to them?
(Shows ~embalmer138 a list of common GameStop.com problems)
~embalmer138: "Track order" was why I was trying to call.
~embalmer138's review of GameStop.com customer service
GetHuman: So how would you sum up your experience for GetHuman's GameStop.com 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.
~embalmer138: i've called a number of times, and waited for over two hours each time without anyone answering. i have a job, can't sit on the phone all day so they can fix their ***** ups. answer your phone!!!!!!!!
GetHuman: Let's quantify your experience contacting GameStop.com. On a scale of 1 to 5, how easy is it go get help on a GameStop.com problem?
~embalmer138: I'd give them a two 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?
~embalmer138: I'd give them a three out of five on communication.
GetHuman: And what about GameStop.com's ability to quickly and effectively address your problem?
~embalmer138: For that I would say four out of five.
GetHuman: And finally- any advice for other GameStop.com customers?
~embalmer138: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for GameStop.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~embalmer138 taken from his GameStop.com customer service problem that occurred on November 23rd, 2017.