Good Housekeeping Magazine: the representative provided a host of informati...
A Good Housekeeping Magazine customer review by GetHuman user ~anon from November 24th, 2017
Background on ~anon's case
GetHuman: ~anon - can you tell our other Good Housekeeping Magazine customers when your case took place?
~anon: Yes. It was afternoon, on November 21st.
GetHuman: Did you reach out to Good Housekeeping Magazine, and if so, how?
GetHuman: And which of these common Good Housekeeping Magazine customer issues best describes the reason you wanted to talk to them?
(Shows ~anon a list of common Good Housekeeping Magazine problems)
~anon: "Refund a Charge" was why I was trying to call.
~anon's review of Good Housekeeping Magazine customer service
GetHuman: So how would you sum up your experience for GetHuman's Good Housekeeping 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.
~anon: the representative provided a host of information about the best way to get a digital edition of the magazine.
GetHuman: Let's quantify your experience contacting Good Housekeeping Magazine. On a scale of 1 to 5, how easy is it go get help on a Good Housekeeping Magazine problem?
~anon: 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?
~anon: I'd give them a five out of five on communication.
GetHuman: And what about Good Housekeeping Magazine's ability to quickly and effectively address your problem?
~anon: For that I would say three out of five.
GetHuman: And finally- any advice for other Good Housekeeping Magazine customers?
~anon: Call them early in the day or late. Don't forget any personal or account information you might need for Good Housekeeping Magazine to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~anon taken from his Good Housekeeping Magazine customer service problem that occurred on November 21st, 2017.