Partsgeek.com: I PURCHASED PARTS PER DESCRPTION AND PICTURE HO...
A Partsgeek.com customer review by GetHuman user ~Rom from November 21st, 2017
Background on ~Rom's case
GetHuman: ~Rom - can you tell our other Partsgeek.com customers when your case took place?
~Rom: Yes I can. It was morning, on November 17th.
GetHuman: Did you reach out to Partsgeek.com, and if so, how?
GetHuman: And which of these common Partsgeek.com customer issues best describes the reason you wanted to talk to them?
(Shows ~Rom a list of common Partsgeek.com problems)
~Rom: "Find a Part" was why I was trying to call.
~Rom's review of Partsgeek.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Partsgeek.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.
~Rom: I PURCHASED PARTS PER DESCRPTION AND PICTURE HOWEVER THEY DO NOT FIT MY CAR.I CREATED CUSTOMER SERVICE TICKET FEW DAYS AGO. THERE IS NO RESPONSE. THEY SAY THEY WILL RECPOND WITHIN ** HOURS. TRIED TO CALL THEM ON TWO DIFFERENT NUMBERS THERE IS NO PERSON SO I LET MESSAGE. I WILL NOT DEAL WITH THEM ANYMORE.
GetHuman: Let's quantify your experience contacting Partsgeek.com. On a scale of 1 to 5, how easy is it go get help on a Partsgeek.com problem?
~Rom: 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?
~Rom: I'd give them a one out of five on communication.
GetHuman: And what about Partsgeek.com's ability to quickly and effectively address your problem?
~Rom: For that I would say three out of five.
GetHuman: And finally- any advice for other Partsgeek.com customers?
~Rom: Call them early in the day or late. Don't forget any personal or account information you might need for Partsgeek.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Rom taken from his Partsgeek.com customer service problem that occurred on November 17th, 2017.