Playstation: I had no trouble understanding the person on th...
Eine Playstation Kundenbewertung durch GetHuman-Benutzer ~Nannooskeeska von November 1., 2017
Background on ~Nannooskeeska's case
GetHuman: ~Nannooskeeska - can you tell our other Playstation customers when your case took place?
~Nannooskeeska: Yes I can. It was afternoon, on Oktober 29..
GetHuman: Did you reach out to Playstation, and if so, how?
GetHuman: And which of these common Playstation customer issues best describes the reason you wanted to talk to them?
(Shows ~Nannooskeeska a list of common Playstation problems)
~Nannooskeeska: "Repairs" was why I was trying to call.
~Nannooskeeska's review of Playstation customer service
GetHuman: So how would you sum up your experience for GetHuman's Playstation 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.
~Nannooskeeska: I had no trouble understanding the person on the other end. Was very helpful, informative, and cheerful. Took a short amount of time to get her on the phone. Overall a good call.
GetHuman: Let's quantify your experience contacting Playstation. On a scale of 1 to 5, how easy is it go get help on a Playstation problem?
~Nannooskeeska: I'd give them a four 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?
~Nannooskeeska: I'd give them a five out of five on communication.
GetHuman: And what about Playstation's ability to quickly and effectively address your problem?
~Nannooskeeska: For that I would say four out of five.
GetHuman: And finally- any advice for other Playstation customers?
~Nannooskeeska: Rufen Sie sie früh am Tag oder spät an. Vergessen Sie nicht alle persönlichen oder Kontoinformationen, die Sie benötigen, damit Playstation weiß, wer Sie sind.
GetHuman: Well there you have it. Some useful feedback and words from ~Nannooskeeska taken from his Playstation customer service problem that occurred on Oktober 29., 2017.