Honeywell: This IS the worse possible service ever receive...
A Honeywell customer review by GetHuman user ~vernmad from November 25th, 2017
Background on ~vernmad's case
GetHuman: ~vernmad - can you tell our other Honeywell customers when your case took place?
~vernmad: Yes I can. It was morning, on November 21st.
GetHuman: Did you reach out to Honeywell, and if so, how?
GetHuman: And which of these common Honeywell customer issues best describes the reason you wanted to talk to them?
(Shows ~vernmad a list of common Honeywell problems)
~vernmad: "Repairs" was why I was trying to call.
~vernmad's review of Honeywell customer service
GetHuman: So how would you sum up your experience for GetHuman's Honeywell 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.
~vernmad: This IS the worse possible service ever received in ** years. I was in customer service industry, and this is the worse run customer service ever. My god HONEYWELL WAKE UP!! Pay me and I will run the service department better than this in * months no problem! You should be ashamed of yourselfs calling yourself a company.
GetHuman: Let's quantify your experience contacting Honeywell. On a scale of 1 to 5, how easy is it go get help on a Honeywell problem?
~vernmad: I'd give them a two 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?
~vernmad: I'd give them a three out of five on communication.
GetHuman: And what about Honeywell's ability to quickly and effectively address your problem?
~vernmad: For that I would say one out of five.
GetHuman: And finally- any advice for other Honeywell customers?
~vernmad: Call them early in the day or late. Don't forget any personal or account information you might need for Honeywell to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~vernmad taken from his Honeywell customer service problem that occurred on November 21st, 2017.