Rowenta: the *** number does not exist, been trying almo...
A Rowenta customer review by GetHuman user ~charlie from November 24th, 2017
Background on ~charlie's case
GetHuman: ~charlie - can you tell our other Rowenta customers when your case took place?
~charlie: Yup. It was evening, on November 21st.
GetHuman: Did you reach out to Rowenta, and if so, how?
GetHuman: And which of these common Rowenta customer issues best describes the reason you wanted to talk to them?
(Shows ~charlie a list of common Rowenta problems)
~charlie: "Warranty claim" was why I was trying to call.
~charlie's review of Rowenta customer service
GetHuman: So how would you sum up your experience for GetHuman's Rowenta 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.
~charlie: the *** number does not exist, been trying almost * weeks now to speak to someone that works for Rowenta, not responding to emails on their Facebook account or the website emails sent.......hard to believe, harder to explain to two of our Clients, the worst customer service I have ever experienced, someone MUST be in charge somewhere in North America??
GetHuman: Let's quantify your experience contacting Rowenta. On a scale of 1 to 5, how easy is it go get help on a Rowenta problem?
~charlie: 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?
~charlie: I'd give them a one out of five on communication.
GetHuman: And what about Rowenta's ability to quickly and effectively address your problem?
~charlie: For that I would say one out of five.
GetHuman: And finally- any advice for other Rowenta customers?
~charlie: Call them early in the day or late. Don't forget any personal or account information you might need for Rowenta to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~charlie taken from his Rowenta customer service problem that occurred on November 21st, 2017.