Electronic Arts: EA trained this guy for * day and threw him out...
A Electronic Arts customer review by GetHuman user ~Alex from November 7th, 2017
Background on ~Alex's case
GetHuman: ~Alex - can you tell our other Electronic Arts customers when your case took place?
~Alex: Sure. It was afternoon, on October 28th.
GetHuman: Did you reach out to Electronic Arts, and if so, how?
GetHuman: And which of these common Electronic Arts customer issues best describes the reason you wanted to talk to them?
(Shows ~Alex a list of common Electronic Arts problems)
~Alex: "Can't Receive Code to Reset" was why I was trying to contact.
~Alex's review of Electronic Arts customer service
GetHuman: So how would you sum up your experience for GetHuman's Electronic Arts 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.
~Alex: EA trained this guy for * day and threw him out to the phones* I was his first call. He struggled a lot and didn't seem to understand my problem, but was very earnest and conversational. We came close to resolving my problem, but he somehow lost the call.
GetHuman: Let's quantify your experience contacting Electronic Arts. On a scale of 1 to 5, how easy is it go get help on a Electronic Arts problem?
~Alex: 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?
~Alex: I'd give them a two out of five on communication.
GetHuman: And what about Electronic Arts's ability to quickly and effectively address your problem?
~Alex: For that I would say one out of five.
GetHuman: And finally- any advice for other Electronic Arts customers?
~Alex: Call them early in the day or late. Don't forget any personal or account information you might need for Electronic Arts to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Alex taken from his Electronic Arts customer service problem that occurred on October 28th, 2017.