Memorex Electronics: THE NUMBER SAID IT WAS AFTER HOURS AT **:**AM*I...
A Memorex Electronics customer review by GetHuman user GetHuman-19001 from November 16th, 2017
Background on GetHuman-19001's case
GetHuman: GetHuman-19001 - can you tell our other Memorex Electronics customers when your case took place?
GetHuman-19001: Sure. It was evening, on November 12th.
GetHuman: Did you reach out to Memorex Electronics, and if so, how?
GetHuman: And which of these common Memorex Electronics customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-19001 a list of common Memorex Electronics problems)
GetHuman-19001: "Returns" was why I was trying to call.
GetHuman-19001's review of Memorex Electronics customer service
GetHuman: So how would you sum up your experience for GetHuman's Memorex Electronics 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-19001: THE NUMBER SAID IT WAS AFTER HOURS AT **:**AM*I DO NOT THINK THAT GEORGIA TIME IS THAT MUCH DIFFERENCE.
GetHuman: Let's quantify your experience contacting Memorex Electronics. On a scale of 1 to 5, how easy is it go get help on a Memorex Electronics problem?
GetHuman-19001: 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-19001: I'd give them a three out of five on communication.
GetHuman: And what about Memorex Electronics's ability to quickly and effectively address your problem?
GetHuman-19001: For that I would say five out of five.
GetHuman: And finally- any advice for other Memorex Electronics customers?
GetHuman-19001: Call them early in the day or late. Don't forget any personal or account information you might need for Memorex Electronics to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-19001 taken from his Memorex Electronics customer service problem that occurred on November 12th, 2017.