Partsgeek.com: I called the number there was a wait time and t...
A Partsgeek.com customer review by GetHuman user ~verna from November 22nd, 2017
Background on ~verna's case
GetHuman: ~verna - can you tell our other Partsgeek.com customers when your case took place?
~verna: Yes. It was late at night, on November 20th.
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 ~verna a list of common Partsgeek.com problems)
~verna: "Refund a Charge" was why I was trying to call.
~verna'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.
~verna: I called the number there was a wait time and then told to leave a message and phone number. Could of spoken to a live person and it would of been more helpful. We want to return an item which is not the one we wanted and need a Return Authorization number to complete the return.
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?
~verna: 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?
~verna: I'd give them a two out of five on communication.
GetHuman: And what about Partsgeek.com's ability to quickly and effectively address your problem?
~verna: For that I would say one out of five.
GetHuman: And finally- any advice for other Partsgeek.com customers?
~verna: 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 ~verna taken from his Partsgeek.com customer service problem that occurred on November 20th, 2017.