Hearthware, Inc.: I called this number at **:**, after being on h...
A Hearthware, Inc. customer review by GetHuman user ~frosty09 from November 25th, 2017
Background on ~frosty09's case
GetHuman: ~frosty09 - can you tell our other Hearthware, Inc. customers when your case took place?
~frosty09: Yes. It was morning, on November 15th.
GetHuman: Did you reach out to Hearthware, Inc., and if so, how?
GetHuman: And which of these common Hearthware, Inc. customer issues best describes the reason you wanted to talk to them?
(Shows ~frosty09 a list of common Hearthware, Inc. problems)
~frosty09: "Complaint" was why I was trying to call.
~frosty09's review of Hearthware, Inc. customer service
GetHuman: So how would you sum up your experience for GetHuman's Hearthware, Inc. 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.
~frosty09: I called this number at **:**, after being on hold for one hour and **-minutes at two other numbers. Young lady was very helpful in cancelling three (*) orders I had placed for NuWave Ovens and accessories.
GetHuman: Let's quantify your experience contacting Hearthware, Inc.. On a scale of 1 to 5, how easy is it go get help on a Hearthware, Inc. problem?
~frosty09: I'd give them a four 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?
~frosty09: I'd give them a one out of five on communication.
GetHuman: And what about Hearthware, Inc.'s ability to quickly and effectively address your problem?
~frosty09: For that I would say two out of five.
GetHuman: And finally- any advice for other Hearthware, Inc. customers?
~frosty09: Call them early in the day or late. Don't forget any personal or account information you might need for Hearthware, Inc. to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~frosty09 taken from his Hearthware, Inc. customer service problem that occurred on November 15th, 2017.