Mail.com: After receiving the same formed email four time...
A Mail.com customer review by GetHuman user ~Unbelievable from November 25th, 2017
Background on ~Unbelievable's case
GetHuman: ~Unbelievable - can you tell our other Mail.com customers when your case took place?
~Unbelievable: Yes I can. It was afternoon, on November 18th.
GetHuman: Did you reach out to Mail.com, and if so, how?
GetHuman: And which of these common Mail.com customer issues best describes the reason you wanted to talk to them?
(Shows ~Unbelievable a list of common Mail.com problems)
~Unbelievable: "Lower my bill" was why I was trying to call.
~Unbelievable's review of Mail.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Mail.com 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.
~Unbelievable: After receiving the same formed email four times I called and got someone from India.. Could not understand him. I had to spell the email address to him three times only for him to tell me he is going to email my complaint to the department I had already contacted.
GetHuman: Let's quantify your experience contacting Mail.com. On a scale of 1 to 5, how easy is it go get help on a Mail.com problem?
~Unbelievable: I'd give them a three 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?
~Unbelievable: I'd give them a two out of five on communication.
GetHuman: And what about Mail.com's ability to quickly and effectively address your problem?
~Unbelievable: For that I would say one out of five.
GetHuman: And finally- any advice for other Mail.com customers?
~Unbelievable: Call them early in the day or late. Don't forget any personal or account information you might need for Mail.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Unbelievable taken from his Mail.com customer service problem that occurred on November 18th, 2017.