Rockstar Games: its amazing there was like no wait and it was a...
A Rockstar Games customer review by GetHuman user ~UnafraidZues36 from November 24th, 2017
Background on ~UnafraidZues36's case
GetHuman: ~UnafraidZues36 - can you tell our other Rockstar Games customers when your case took place?
~UnafraidZues36: Yup. It was morning, on November 14th.
GetHuman: Did you reach out to Rockstar Games, and if so, how?
GetHuman: And which of these common Rockstar Games customer issues best describes the reason you wanted to talk to them?
(Shows ~UnafraidZues36 a list of common Rockstar Games problems)
~UnafraidZues36: "Refund a Charge" was why I was trying to contact.
~UnafraidZues36's review of Rockstar Games customer service
GetHuman: So how would you sum up your experience for GetHuman's Rockstar Games 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.
~UnafraidZues36: its amazing there was like no wait and it was a very nice and they will repeat what they said in a louder voice if you did not understand or hear it that well
GetHuman: Let's quantify your experience contacting Rockstar Games. On a scale of 1 to 5, how easy is it go get help on a Rockstar Games problem?
~UnafraidZues36: 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?
~UnafraidZues36: I'd give them a two out of five on communication.
GetHuman: And what about Rockstar Games's ability to quickly and effectively address your problem?
~UnafraidZues36: For that I would say one out of five.
GetHuman: And finally- any advice for other Rockstar Games customers?
~UnafraidZues36: Call them early in the day or late. Don't forget any personal or account information you might need for Rockstar Games to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~UnafraidZues36 taken from his Rockstar Games customer service problem that occurred on November 14th, 2017.