Lexmark: After a few automated questions, got to a perso...
A Lexmark customer review by GetHuman user ~Glenno from November 11th, 2017
Background on ~Glenno's case
GetHuman: ~Glenno - can you tell our other Lexmark customers when your case took place?
~Glenno: Yes. It was afternoon, on November 6th.
GetHuman: Did you reach out to Lexmark, and if so, how?
GetHuman: And which of these common Lexmark customer issues best describes the reason you wanted to talk to them?
(Shows ~Glenno a list of common Lexmark problems)
~Glenno: "Where to buy" was why I was trying to call.
~Glenno's review of Lexmark customer service
GetHuman: So how would you sum up your experience for GetHuman's Lexmark 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.
~Glenno: After a few automated questions, got to a person without any hold. She was incredibly helpful and thorough, going above and beyond what was necessary or expected -- especially since my printer was out of warranty already. I was most impressed. I don't know if everyone in the department is this good, but it was among the best customer service I've gotten.
GetHuman: Let's quantify your experience contacting Lexmark. On a scale of 1 to 5, how easy is it go get help on a Lexmark problem?
~Glenno: 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?
~Glenno: I'd give them a two out of five on communication.
GetHuman: And what about Lexmark's ability to quickly and effectively address your problem?
~Glenno: For that I would say one out of five.
GetHuman: And finally- any advice for other Lexmark customers?
~Glenno: Call them early in the day or late. Don't forget any personal or account information you might need for Lexmark to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Glenno taken from his Lexmark customer service problem that occurred on November 6th, 2017.