M2 Media Group: I did not even sign up for a magazine and got a...
A M2 Media Group customer review by GetHuman user GetHuman-229333 from November 12th, 2017
Background on GetHuman-229333's case
GetHuman: GetHuman-229333 - can you tell our other M2 Media Group customers when your case took place?
GetHuman-229333: Yup. It was evening, on November 9th.
GetHuman: Did you reach out to M2 Media Group, and if so, how?
GetHuman: And which of these common M2 Media Group customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-229333 a list of common M2 Media Group problems)
GetHuman-229333: "Delivery problem" was why I was trying to contact.
GetHuman-229333's review of M2 Media Group customer service
GetHuman: So how would you sum up your experience for GetHuman's M2 Media Group 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-229333: I did not even sign up for a magazine and got a run-around with different numbers to call to cancel. There is no one to talk to at this number.
GetHuman: Let's quantify your experience contacting M2 Media Group. On a scale of 1 to 5, how easy is it go get help on a M2 Media Group problem?
GetHuman-229333: I'd give them a four 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-229333: I'd give them a three out of five on communication.
GetHuman: And what about M2 Media Group's ability to quickly and effectively address your problem?
GetHuman-229333: For that I would say five out of five.
GetHuman: And finally- any advice for other M2 Media Group customers?
GetHuman-229333: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for M2 Media Group to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-229333 taken from his M2 Media Group customer service problem that occurred on November 9th, 2017.