Fingerhut: it was like talking to" peggy" from the capital...
A Fingerhut customer review by GetHuman user ~maxx from November 5th, 2017
Background on ~maxx's case
GetHuman: ~maxx - can you tell our other Fingerhut customers when your case took place?
~maxx: Yes. It was morning, on October 29th.
GetHuman: Did you reach out to Fingerhut, and if so, how?
GetHuman: And which of these common Fingerhut customer issues best describes the reason you wanted to talk to them?
(Shows ~maxx a list of common Fingerhut problems)
~maxx: "Cancel Order" was why I was trying to call.
~maxx's review of Fingerhut customer service
GetHuman: So how would you sum up your experience for GetHuman's Fingerhut 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.
~maxx: it was like talking to" peggy" from the capital one commercial. still have money in cyberspace and none in my pocket, plus they said i would be charged a late fee, when they had a comp. clitch that wouldnt except my credit card, *and my credit card people think that it went through so they took the money out of my credit line. good luck to all who read this.
GetHuman: Let's quantify your experience contacting Fingerhut. On a scale of 1 to 5, how easy is it go get help on a Fingerhut problem?
~maxx: I'd give them a two 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?
~maxx: I'd give them a five out of five on communication.
GetHuman: And what about Fingerhut's ability to quickly and effectively address your problem?
~maxx: For that I would say two out of five.
GetHuman: And finally- any advice for other Fingerhut customers?
~maxx: Call them early in the day or late. Don't forget any personal or account information you might need for Fingerhut to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~maxx taken from his Fingerhut customer service problem that occurred on October 29th, 2017.