Electronic Arts: i had to wait very long time in between respons...
A Electronic Arts customer review by GetHuman user ~KINGREAPER69 from November 18th, 2017
Background on ~KINGREAPER69's case
GetHuman: ~KINGREAPER69 - can you tell our other Electronic Arts customers when your case took place?
~KINGREAPER69: Yes I can. It was middle of the night, on November 16th.
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 ~KINGREAPER69 a list of common Electronic Arts problems)
~KINGREAPER69: "Technical Support" was why I was trying to contact.
~KINGREAPER69'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.
~KINGREAPER69: i had to wait very long time in between responses and it felt like i was talking to a computer. Very convinced that it was automated. NOT GOOD AT ALL
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?
~KINGREAPER69: 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?
~KINGREAPER69: I'd give them a five out of five on communication.
GetHuman: And what about Electronic Arts's ability to quickly and effectively address your problem?
~KINGREAPER69: For that I would say one out of five.
GetHuman: And finally- any advice for other Electronic Arts customers?
~KINGREAPER69: 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 ~KINGREAPER69 taken from his Electronic Arts customer service problem that occurred on November 16th, 2017.