Harborfreight.com: Dont expect to get parts for any of their motor...
A Harborfreight.com customer review by GetHuman user ~jerwvs from November 20th, 2017
Background on ~jerwvs's case
GetHuman: ~jerwvs - can you tell our other Harborfreight.com customers when your case took place?
~jerwvs: Yeah. It was middle of the night, on November 13th.
GetHuman: Did you reach out to Harborfreight.com, and if so, how?
GetHuman: And which of these common Harborfreight.com customer issues best describes the reason you wanted to talk to them?
(Shows ~jerwvs a list of common Harborfreight.com problems)
~jerwvs: "Warranty claim" was why I was trying to call.
~jerwvs's review of Harborfreight.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Harborfreight.com 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.
~jerwvs: Dont expect to get parts for any of their motorized tools. I bought a little compressor and the only thing it needs is a compression ring for the piston. All of them have been "discontinued".
GetHuman: Let's quantify your experience contacting Harborfreight.com. On a scale of 1 to 5, how easy is it go get help on a Harborfreight.com problem?
~jerwvs: 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?
~jerwvs: I'd give them a one out of five on communication.
GetHuman: And what about Harborfreight.com's ability to quickly and effectively address your problem?
~jerwvs: For that I would say two out of five.
GetHuman: And finally- any advice for other Harborfreight.com customers?
~jerwvs: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Harborfreight.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~jerwvs taken from his Harborfreight.com customer service problem that occurred on November 13th, 2017.