MagicJack: Called because they took * $** charges off my c...
A MagicJack customer review by GetHuman user GetHuman-203266 from November 13th, 2017
Background on GetHuman-203266's case
GetHuman: GetHuman-203266 - can you tell our other MagicJack customers when your case took place?
GetHuman-203266: Sure. It was middle of the night, on November 4th.
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-203266 a list of common MagicJack problems)
GetHuman-203266: "Dispute a Charge" was why I was trying to call.
GetHuman-203266'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-203266: Called because they took * $** charges off my cc and they were rude, hateful, didn't refund my money,and to top it off they hung up on me. They just lost my business and defiantly will not recommend using them.
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-203266: 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-203266: 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-203266: For that I would say three out of five.
GetHuman: And finally- any advice for other MagicJack customers?
GetHuman-203266: 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-203266 taken from his MagicJack customer service problem that occurred on November 4th, 2017.