MagicJack: customer service is brain dead and that's being...
A MagicJack customer review by GetHuman user ~dusty from November 19th, 2017
Background on ~dusty's case
GetHuman: ~dusty - can you tell our other MagicJack customers when your case took place?
~dusty: Sure. It was afternoon, on November 16th.
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 ~dusty a list of common MagicJack problems)
~dusty: "Dispute a Charge" was why I was trying to call.
~dusty'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.
~dusty: customer service is brain dead and that's being polite. No matter how you explain the problem. they say I am sorry and go off on a tangent or transfer you to a more "qualified" person until they just disconnect. I am not sure that if I pay them the $** to port my number to another carrier That they are skilled enough to do it. Stay away!
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?
~dusty: 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?
~dusty: I'd give them a two out of five on communication.
GetHuman: And what about MagicJack's ability to quickly and effectively address your problem?
~dusty: For that I would say five out of five.
GetHuman: And finally- any advice for other MagicJack customers?
~dusty: 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 ~dusty taken from his MagicJack customer service problem that occurred on November 16th, 2017.