Oprah Magazine: I had e-mailed * days before with no response s...
A Oprah Magazine customer review by GetHuman user ~Portland Coates from November 24th, 2017
Background on ~Portland Coates's case
GetHuman: ~Portland Coates - can you tell our other Oprah Magazine customers when your case took place?
~Portland Coates: Yeah. It was middle of the night, on November 23rd.
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 ~Portland Coates a list of common Oprah Magazine problems)
~Portland Coates: "Cancel my subscription" was why I was trying to call.
~Portland Coates'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.
~Portland Coates: I had e-mailed * days before with no response so this "solved" the issue of what happened right away. Thanks. Portland
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?
~Portland Coates: 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?
~Portland Coates: I'd give them a two out of five on communication.
GetHuman: And what about Oprah Magazine's ability to quickly and effectively address your problem?
~Portland Coates: For that I would say three out of five.
GetHuman: And finally- any advice for other Oprah Magazine customers?
~Portland Coates: 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 ~Portland Coates taken from his Oprah Magazine customer service problem that occurred on November 23rd, 2017.