Electronic Arts: Used Skype, been on hold for over * hours with...
A Electronic Arts customer review by GetHuman user GetHuman-77219 from November 16th, 2017
Background on GetHuman-77219's case
GetHuman: GetHuman-77219 - can you tell our other Electronic Arts customers when your case took place?
GetHuman-77219: Yes. It was middle of the night, on November 7th.
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 GetHuman-77219 a list of common Electronic Arts problems)
GetHuman-77219: "In Game Problem" was why I was trying to contact.
GetHuman-77219'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.
GetHuman-77219: Used Skype, been on hold for over * hours with no response. Can't access my account without talking to anyone...but can't talk to anyone.
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?
GetHuman-77219: 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?
GetHuman-77219: 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?
GetHuman-77219: For that I would say four out of five.
GetHuman: And finally- any advice for other Electronic Arts customers?
GetHuman-77219: 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 GetHuman-77219 taken from his Electronic Arts customer service problem that occurred on November 7th, 2017.