MagicJack: I renewed my magic jack for * years and was tol...
A MagicJack customer review by GetHuman user GetHuman-165812 from November 24th, 2017
Background on GetHuman-165812's case
GetHuman: GetHuman-165812 - can you tell our other MagicJack customers when your case took place?
GetHuman-165812: Yeah. It was late at night, on November 18th.
GetHuman: Did you reach out to MagicJack, and if so, how?
GetHuman: And which of these common MagicJack customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-165812 a list of common MagicJack problems)
GetHuman-165812: "Account Access" was why I was trying to call.
GetHuman-165812's review of MagicJack customer service
GetHuman: So how would you sum up your experience for GetHuman's MagicJack 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-165812: I renewed my magic jack for * years and was told that it would be up and running after I disconnected it for * minutes and then reconnected it. I told them that I wanted it working before we ended our session and they disconnected me!
GetHuman: Let's quantify your experience contacting MagicJack. On a scale of 1 to 5, how easy is it go get help on a MagicJack problem?
GetHuman-165812: 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?
GetHuman-165812: I'd give them a one out of five on communication.
GetHuman: And what about MagicJack's ability to quickly and effectively address your problem?
GetHuman-165812: For that I would say three out of five.
GetHuman: And finally- any advice for other MagicJack customers?
GetHuman-165812: Call them early in the day or late. Don't forget any personal or account information you might need for MagicJack to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-165812 taken from his MagicJack customer service problem that occurred on November 18th, 2017.