M2 Media Group: Rep apologized. Cancelled subscription, credite...
A M2 Media Group customer review by GetHuman user ~genemitchell from November 27th, 2017
Background on ~genemitchell's case
GetHuman: ~genemitchell - can you tell our other M2 Media Group customers when your case took place?
~genemitchell: Yes I can. It was morning, on November 22nd.
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 ~genemitchell a list of common M2 Media Group problems)
~genemitchell: "Delivery problem" was why I was trying to contact.
~genemitchell'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.
~genemitchell: Rep apologized. Cancelled subscription, credited my account and offered to halt other auto-renewal subscriptions that were pending.*Very nice and pleasant
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?
~genemitchell: I'd give them a five 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?
~genemitchell: I'd give them a five out of five on communication.
GetHuman: And what about M2 Media Group's ability to quickly and effectively address your problem?
~genemitchell: For that I would say three out of five.
GetHuman: And finally- any advice for other M2 Media Group customers?
~genemitchell: 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 ~genemitchell taken from his M2 Media Group customer service problem that occurred on November 22nd, 2017.