Pogo - EA Games: pogo communication is awful. four years ago i...
A Pogo - EA Games customer review by GetHuman user ~alistorm from November 22nd, 2017
Background on ~alistorm's case
GetHuman: ~alistorm - can you tell our other Pogo - EA Games customers when your case took place?
~alistorm: Yes I can. It was morning, on November 20th.
GetHuman: Did you reach out to Pogo - EA Games, and if so, how?
GetHuman: And which of these common Pogo - EA Games customer issues best describes the reason you wanted to talk to them?
(Shows ~alistorm a list of common Pogo - EA Games problems)
~alistorm: "In Game Problem" was why I was trying to contact.
~alistorm's review of Pogo - EA Games customer service
GetHuman: So how would you sum up your experience for GetHuman's Pogo - EA 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.
~alistorm: pogo communication is awful. four years ago it was so much easier to get ahold of a representative. my email is smilindixie@hotmail if someone with authority to do something can get ahold of me.
GetHuman: Let's quantify your experience contacting Pogo - EA Games. On a scale of 1 to 5, how easy is it go get help on a Pogo - EA Games problem?
~alistorm: 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?
~alistorm: I'd give them a one out of five on communication.
GetHuman: And what about Pogo - EA Games's ability to quickly and effectively address your problem?
~alistorm: For that I would say three out of five.
GetHuman: And finally- any advice for other Pogo - EA Games customers?
~alistorm: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Pogo - EA Games to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~alistorm taken from his Pogo - EA Games customer service problem that occurred on November 20th, 2017.