Lennox: You keep leaving messages with customer service...
A Lennox customer review by GetHuman user GetHuman-122093 from November 1st, 2017
Background on GetHuman-122093's case
GetHuman: GetHuman-122093 - can you tell our other Lennox customers when your case took place?
GetHuman-122093: Yup. It was middle of the night, on October 27th.
GetHuman: Did you reach out to Lennox, and if so, how?
GetHuman: And which of these common Lennox customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-122093 a list of common Lennox problems)
GetHuman-122093: "Where to buy" was why I was trying to call.
GetHuman-122093's review of Lennox customer service
GetHuman: So how would you sum up your experience for GetHuman's Lennox 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-122093: You keep leaving messages with customer service to call back and they dont call back.*Being trying to get a feed back on a claim for the past * months (* calls total) to no avail. Will never again will use this company and will discourage others
GetHuman: Let's quantify your experience contacting Lennox. On a scale of 1 to 5, how easy is it go get help on a Lennox problem?
GetHuman-122093: 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-122093: I'd give them a one out of five on communication.
GetHuman: And what about Lennox's ability to quickly and effectively address your problem?
GetHuman-122093: For that I would say three out of five.
GetHuman: And finally- any advice for other Lennox customers?
GetHuman-122093: Call them early in the day or late. Don't forget any personal or account information you might need for Lennox to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-122093 taken from his Lennox customer service problem that occurred on October 27th, 2017.