Partsgeek.com: no one ever answered...sent the wrong parts...h...
Una recensione del cliente Partsgeek.com da parte dell'utente GetHuman ~anthony da novembre 18º, 2017
Background on ~anthony's case
GetHuman: ~anthony - can you tell our other Partsgeek.com customers when your case took place?
~anthony: Yes. It was morning, on novembre 16º.
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 ~anthony a list of common Partsgeek.com problems)
~anthony: "Refund a Charge" was why I was trying to call.
~anthony'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.
~anthony: no one ever answered...sent the wrong parts...how after I put in all the info asked for? now im stranded...never use them again.i should of went to pep boys or auto zone and paid a little more it would of been well worth it...
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?
~anthony: I'd give them a one 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?
~anthony: I'd give them a three out of five on communication.
GetHuman: And what about Partsgeek.com's ability to quickly and effectively address your problem?
~anthony: For that I would say four out of five.
GetHuman: And finally- any advice for other Partsgeek.com customers?
~anthony: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per Partsgeek.com sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~anthony taken from his Partsgeek.com customer service problem that occurred on novembre 16º, 2017.