Lowe's: lowes customer care is horrible i had to call t...
A Lowe's customer review by GetHuman user GetHuman-437585 from November 17th, 2017
Background on GetHuman-437585's case
GetHuman: GetHuman-437585 - can you tell our other Lowe's customers when your case took place?
GetHuman-437585: Yes I can. It was middle of the night, on November 10th.
GetHuman: Did you reach out to Lowe's, and if so, how?
GetHuman: And which of these common Lowe's customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-437585 a list of common Lowe's problems)
GetHuman-437585: "Warranty" was why I was trying to call.
GetHuman-437585's review of Lowe's customer service
GetHuman: So how would you sum up your experience for GetHuman's Lowe's 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-437585: lowes customer care is horrible i had to call them every day for five days trying to get washer fixed that had warranty,still waiting to see what they are going to do,new mexico location,will not buy anything foreign made again no service techs in ohio
GetHuman: Let's quantify your experience contacting Lowe's. On a scale of 1 to 5, how easy is it go get help on a Lowe's problem?
GetHuman-437585: I'd give them a five 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-437585: I'd give them a three out of five on communication.
GetHuman: And what about Lowe's's ability to quickly and effectively address your problem?
GetHuman-437585: For that I would say two out of five.
GetHuman: And finally- any advice for other Lowe's customers?
GetHuman-437585: Call them early in the day or late. Don't forget any personal or account information you might need for Lowe's to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-437585 taken from his Lowe's customer service problem that occurred on November 10th, 2017.