MagicJack: After unsuccessfully going through the chat sup...
A MagicJack customer review by GetHuman user ~lgaston65 from November 22nd, 2017
Background on ~lgaston65's case
GetHuman: ~lgaston65 - can you tell our other MagicJack customers when your case took place?
~lgaston65: Yup. It was afternoon, on November 13th.
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 ~lgaston65 a list of common MagicJack problems)
~lgaston65: "Dispute a Charge" was why I was trying to call.
~lgaston65'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.
~lgaston65: After unsuccessfully going through the chat support for * months and still receiving poor quality service through the device, the company said they cannot refund my money (any portion of it). And I paid for * years worth of service (over $***!). I am following up with their management.
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?
~lgaston65: 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?
~lgaston65: I'd give them a four out of five on communication.
GetHuman: And what about MagicJack's ability to quickly and effectively address your problem?
~lgaston65: For that I would say five out of five.
GetHuman: And finally- any advice for other MagicJack customers?
~lgaston65: 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 ~lgaston65 taken from his MagicJack customer service problem that occurred on November 13th, 2017.