Oprah Magazine: It seemed so easy. I called to cancel my subscr...
A Oprah Magazine customer review by GetHuman user GetHuman-171527 from November 14th, 2017
Background on GetHuman-171527's case
GetHuman: GetHuman-171527 - can you tell our other Oprah Magazine customers when your case took place?
GetHuman-171527: Yeah. It was afternoon, on November 12th.
GetHuman: Did you reach out to Oprah Magazine, and if so, how?
GetHuman: And which of these common Oprah Magazine customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-171527 a list of common Oprah Magazine problems)
GetHuman-171527: "I'm moving" was why I was trying to call.
GetHuman-171527's review of Oprah Magazine customer service
GetHuman: So how would you sum up your experience for GetHuman's Oprah Magazine 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-171527: It seemed so easy. I called to cancel my subscription because of hardship at home. Matt was AWESOME. He took care of it right then and there. Thanks Matt
GetHuman: Let's quantify your experience contacting Oprah Magazine. On a scale of 1 to 5, how easy is it go get help on a Oprah Magazine problem?
GetHuman-171527: 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?
GetHuman-171527: I'd give them a five out of five on communication.
GetHuman: And what about Oprah Magazine's ability to quickly and effectively address your problem?
GetHuman-171527: For that I would say five out of five.
GetHuman: And finally- any advice for other Oprah Magazine customers?
GetHuman-171527: Call them early in the day or late. Don't forget any personal or account information you might need for Oprah Magazine to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-171527 taken from his Oprah Magazine customer service problem that occurred on November 12th, 2017.