Philips Norelco: After viewing your lastest Norelco ad for razor...
A Philips Norelco customer review by GetHuman user GetHuman-257118 from November 16th, 2017
Background on GetHuman-257118's case
GetHuman: GetHuman-257118 - can you tell our other Philips Norelco customers when your case took place?
GetHuman-257118: Yup. It was afternoon, on November 11th.
GetHuman: Did you reach out to Philips Norelco, and if so, how?
GetHuman: And which of these common Philips Norelco customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-257118 a list of common Philips Norelco problems)
GetHuman-257118: "Repairs" was why I was trying to call.
GetHuman-257118's review of Philips Norelco customer service
GetHuman: So how would you sum up your experience for GetHuman's Philips Norelco 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-257118: After viewing your lastest Norelco ad for razors, I will never again buy a Philips Norelco product. I found the ad to be offensive and vulgar.
GetHuman: Let's quantify your experience contacting Philips Norelco. On a scale of 1 to 5, how easy is it go get help on a Philips Norelco problem?
GetHuman-257118: I'd give them a three 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-257118: I'd give them a five out of five on communication.
GetHuman: And what about Philips Norelco's ability to quickly and effectively address your problem?
GetHuman-257118: For that I would say five out of five.
GetHuman: And finally- any advice for other Philips Norelco customers?
GetHuman-257118: Call them early in the day or late. Don't forget any personal or account information you might need for Philips Norelco to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-257118 taken from his Philips Norelco customer service problem that occurred on November 11th, 2017.