Philips Norelco: Lady was extremely helpful. I lost my charger...
A Philips Norelco customer review by GetHuman user ~Paul Singleton from November 19th, 2017
Background on ~Paul Singleton's case
GetHuman: ~Paul Singleton - can you tell our other Philips Norelco customers when your case took place?
~Paul Singleton: Yeah. It was middle of the night, on November 13th.
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 ~Paul Singleton a list of common Philips Norelco problems)
~Paul Singleton: "Technical support" was why I was trying to call.
~Paul Singleton'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.
~Paul Singleton: Lady was extremely helpful. I lost my charger stand. She's going to mail me a new one free of charge! I couldn't be happier!
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?
~Paul Singleton: 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?
~Paul Singleton: I'd give them a three out of five on communication.
GetHuman: And what about Philips Norelco's ability to quickly and effectively address your problem?
~Paul Singleton: For that I would say two out of five.
GetHuman: And finally- any advice for other Philips Norelco customers?
~Paul Singleton: 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 ~Paul Singleton taken from his Philips Norelco customer service problem that occurred on November 13th, 2017.