Pogo - EA Games: If you are having problems with POGO.. you cann...
A Pogo - EA Games customer review by GetHuman user ~execgroup from November 14th, 2017
Background on ~execgroup's case
GetHuman: ~execgroup - can you tell our other Pogo - EA Games customers when your case took place?
~execgroup: Yeah. It was afternoon, on November 5th.
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 ~execgroup a list of common Pogo - EA Games problems)
~execgroup: "Banned Account" was why I was trying to contact.
~execgroup'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.
~execgroup: If you are having problems with POGO.. you cannot use this number because there is a recording.. "Problems with POGO.. go to their internet" GOOD BYE... yes that is what they say goodbye and hang up
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?
~execgroup: I'd give them a one 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?
~execgroup: 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?
~execgroup: For that I would say two out of five.
GetHuman: And finally- any advice for other Pogo - EA Games customers?
~execgroup: 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 ~execgroup taken from his Pogo - EA Games customer service problem that occurred on November 5th, 2017.