Kwikset: I waited ** minutes on hold with no time counte...
A Kwikset customer review by GetHuman user GetHuman-392107 from November 20th, 2017
Background on GetHuman-392107's case
GetHuman: GetHuman-392107 - can you tell our other Kwikset customers when your case took place?
GetHuman-392107: Yeah. It was afternoon, on November 16th.
GetHuman: Did you reach out to Kwikset, and if so, how?
GetHuman: And which of these common Kwikset customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-392107 a list of common Kwikset problems)
GetHuman-392107: "Track order" was why I was trying to call.
GetHuman-392107's review of Kwikset customer service
GetHuman: So how would you sum up your experience for GetHuman's Kwikset 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.
GetHuman-392107: I waited ** minutes on hold with no time counter or any indication from Kwikset that they want to keep my business. Imagine a making a lifetime guarantee but not having any way to get any customer service help. After ** minutes of wasting my time I hung up.
GetHuman: Let's quantify your experience contacting Kwikset. On a scale of 1 to 5, how easy is it go get help on a Kwikset problem?
GetHuman-392107: 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?
GetHuman-392107: I'd give them a two out of five on communication.
GetHuman: And what about Kwikset's ability to quickly and effectively address your problem?
GetHuman-392107: For that I would say one out of five.
GetHuman: And finally- any advice for other Kwikset customers?
GetHuman-392107: Call them early in the day or late. Don't forget any personal or account information you might need for Kwikset to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-392107 taken from his Kwikset customer service problem that occurred on November 16th, 2017.