Publisher's Clearing House: This took much less time than I anticipated. A...
A Publisher's Clearing House customer review by GetHuman user ~ml from November 14th, 2017
Background on ~ml's case
GetHuman: ~ml - can you tell our other Publisher's Clearing House customers when your case took place?
~ml: Yes. It was morning, on November 6th.
GetHuman: Did you reach out to Publisher's Clearing House, and if so, how?
GetHuman: And which of these common Publisher's Clearing House customer issues best describes the reason you wanted to talk to them?
(Shows ~ml a list of common Publisher's Clearing House problems)
~ml: "Cancel Account" was why I was trying to call.
~ml's review of Publisher's Clearing House customer service
GetHuman: So how would you sum up your experience for GetHuman's Publisher's Clearing House 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.
~ml: This took much less time than I anticipated. As long as this shows up on my account within ** hours as promised, this was excellent customer service.
GetHuman: Let's quantify your experience contacting Publisher's Clearing House. On a scale of 1 to 5, how easy is it go get help on a Publisher's Clearing House problem?
~ml: I'd give them a three 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?
~ml: I'd give them a four out of five on communication.
GetHuman: And what about Publisher's Clearing House's ability to quickly and effectively address your problem?
~ml: For that I would say five out of five.
GetHuman: And finally- any advice for other Publisher's Clearing House customers?
~ml: Call them early in the day or late. Don't forget any personal or account information you might need for Publisher's Clearing House to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~ml taken from his Publisher's Clearing House customer service problem that occurred on November 6th, 2017.