Pogo - EA Games: I TRIED AND TRIED TO CHANGE MY POGO PASSWORD SI...
A Pogo - EA Games customer review by GetHuman user ~tinkanz7 from November 21st, 2017
Background on ~tinkanz7's case
GetHuman: ~tinkanz7 - can you tell our other Pogo - EA Games customers when your case took place?
~tinkanz7: Yup. It was evening, on November 17th.
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 ~tinkanz7 a list of common Pogo - EA Games problems)
~tinkanz7: "Problem With the App" was why I was trying to contact.
~tinkanz7'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.
~tinkanz7: I TRIED AND TRIED TO CHANGE MY POGO PASSWORD SINCE I DON'T REMEMBER WHAT IT IS. THEN I CHANGED IT AND POGO SAID IT WAS GOOD THEN, JUST TRY TO GET IN AND NADA. I HAVE PAID AND PAID. THIS TRULY *****.
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?
~tinkanz7: 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?
~tinkanz7: 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?
~tinkanz7: For that I would say two out of five.
GetHuman: And finally- any advice for other Pogo - EA Games customers?
~tinkanz7: 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 ~tinkanz7 taken from his Pogo - EA Games customer service problem that occurred on November 17th, 2017.