Harland Clarke: PUT ON HOLD AND THEN CUT OFF ON TWO CONSECUTIVE...
A Harland Clarke customer review by GetHuman user ~SPINVILLAGE from November 25th, 2017
Background on ~SPINVILLAGE's case
GetHuman: ~SPINVILLAGE - can you tell our other Harland Clarke customers when your case took place?
~SPINVILLAGE: Sure. It was middle of the night, on November 20th.
GetHuman: Did you reach out to Harland Clarke, and if so, how?
GetHuman: And which of these common Harland Clarke customer issues best describes the reason you wanted to talk to them?
(Shows ~SPINVILLAGE a list of common Harland Clarke problems)
~SPINVILLAGE: "None of those really matches why I wanted to call Harland Clarke that day." was why I was trying to call.
~SPINVILLAGE's review of Harland Clarke customer service
GetHuman: So how would you sum up your experience for GetHuman's Harland Clarke 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.
~SPINVILLAGE: PUT ON HOLD AND THEN CUT OFF ON TWO CONSECUTIVE OCCASIONS. THEN THREE WEEKS TO RECEIVE THE SIMPLE MAIL ORDER. NEVER AGAIN.
GetHuman: Let's quantify your experience contacting Harland Clarke. On a scale of 1 to 5, how easy is it go get help on a Harland Clarke problem?
~SPINVILLAGE: I'd give them a four 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?
~SPINVILLAGE: I'd give them a one out of five on communication.
GetHuman: And what about Harland Clarke's ability to quickly and effectively address your problem?
~SPINVILLAGE: For that I would say two out of five.
GetHuman: And finally- any advice for other Harland Clarke customers?
~SPINVILLAGE: Call them early in the day or late. Don't forget any personal or account information you might need for Harland Clarke to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~SPINVILLAGE taken from his Harland Clarke customer service problem that occurred on November 20th, 2017.