Reader's Digest: This number actually worked great! Less than a...
A Reader's Digest customer review by GetHuman user GetHuman-17508 from November 23rd, 2017
Background on GetHuman-17508's case
GetHuman: GetHuman-17508 - can you tell our other Reader's Digest customers when your case took place?
GetHuman-17508: Yup. It was middle of the night, on November 21st.
GetHuman: Did you reach out to Reader's Digest, and if so, how?
GetHuman: And which of these common Reader's Digest customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-17508 a list of common Reader's Digest problems)
GetHuman-17508: "Transfer Service" was why I was trying to call.
GetHuman-17508's review of Reader's Digest customer service
GetHuman: So how would you sum up your experience for GetHuman's Reader's Digest 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-17508: This number actually worked great! Less than a minute on hold and didn't have to punch through an automated attendant to speak with a rep.
GetHuman: Let's quantify your experience contacting Reader's Digest. On a scale of 1 to 5, how easy is it go get help on a Reader's Digest problem?
GetHuman-17508: 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-17508: I'd give them a five out of five on communication.
GetHuman: And what about Reader's Digest's ability to quickly and effectively address your problem?
GetHuman-17508: For that I would say four out of five.
GetHuman: And finally- any advice for other Reader's Digest customers?
GetHuman-17508: Call them early in the day or late. Don't forget any personal or account information you might need for Reader's Digest to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-17508 taken from his Reader's Digest customer service problem that occurred on November 21st, 2017.