Monoprice.com: Excellent. Problem was resolved by a CSR in Cal...
A Monoprice.com customer review by GetHuman user ~jamescyberjoe from November 11th, 2017
Background on ~jamescyberjoe's case
GetHuman: ~jamescyberjoe - can you tell our other Monoprice.com customers when your case took place?
~jamescyberjoe: Yup. It was middle of the night, on November 6th.
GetHuman: Did you reach out to Monoprice.com, and if so, how?
GetHuman: And which of these common Monoprice.com customer issues best describes the reason you wanted to talk to them?
(Shows ~jamescyberjoe a list of common Monoprice.com problems)
~jamescyberjoe: "Make a purchase" was why I was trying to call.
~jamescyberjoe's review of Monoprice.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Monoprice.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.
~jamescyberjoe: Excellent. Problem was resolved by a CSR in California. Sorry but using their chat system, like most others is frustrating. I always prefer to talk to someone in the USA.
GetHuman: Let's quantify your experience contacting Monoprice.com. On a scale of 1 to 5, how easy is it go get help on a Monoprice.com problem?
~jamescyberjoe: 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?
~jamescyberjoe: I'd give them a two out of five on communication.
GetHuman: And what about Monoprice.com's ability to quickly and effectively address your problem?
~jamescyberjoe: For that I would say one out of five.
GetHuman: And finally- any advice for other Monoprice.com customers?
~jamescyberjoe: Call them early in the day or late. Don't forget any personal or account information you might need for Monoprice.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~jamescyberjoe taken from his Monoprice.com customer service problem that occurred on November 6th, 2017.