Publisher's Clearing House: She was very patient, thorough, and thank god b...
A Publisher's Clearing House customer review by GetHuman user ~Swan from November 3rd, 2017
Background on ~Swan's case
GetHuman: ~Swan - can you tell our other Publisher's Clearing House customers when your case took place?
~Swan: Yes. It was morning, on October 26th.
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 ~Swan a list of common Publisher's Clearing House problems)
~Swan: "Cancel Account" was why I was trying to call.
~Swan'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.
~Swan: She was very patient, thorough, and thank god because I don't rarely have such an easy phone transaction with other sellers.
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?
~Swan: 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?
~Swan: I'd give them a two out of five on communication.
GetHuman: And what about Publisher's Clearing House's ability to quickly and effectively address your problem?
~Swan: For that I would say five out of five.
GetHuman: And finally- any advice for other Publisher's Clearing House customers?
~Swan: 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 ~Swan taken from his Publisher's Clearing House customer service problem that occurred on October 26th, 2017.