Mail.com: The gentleman that answer understood me and und...
A Mail.com customer review by GetHuman user GetHuman-356125 from November 11th, 2017
Background on GetHuman-356125's case
GetHuman: GetHuman-356125 - can you tell our other Mail.com customers when your case took place?
GetHuman-356125: Yes I can. It was morning, on November 9th.
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 GetHuman-356125 a list of common Mail.com problems)
GetHuman-356125: "Service problem" was why I was trying to call.
GetHuman-356125'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.
GetHuman-356125: The gentleman that answer understood me and understood my desperation to lock my account. I have been hacked! He promised to lock the account immediately and will contact me via another email I set up. Also reported issue for investigation.
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?
GetHuman-356125: 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-356125: I'd give them a four out of five on communication.
GetHuman: And what about Mail.com's ability to quickly and effectively address your problem?
GetHuman-356125: For that I would say one out of five.
GetHuman: And finally- any advice for other Mail.com customers?
GetHuman-356125: 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 GetHuman-356125 taken from his Mail.com customer service problem that occurred on November 9th, 2017.