Philips Electronics: After waiting though a lot of bad music and rep...
A Philips Electronics customer review by GetHuman user ~Fran from November 19th, 2017
Background on ~Fran's case
GetHuman: ~Fran - can you tell our other Philips Electronics customers when your case took place?
~Fran: Yup. It was middle of the night, on November 11th.
GetHuman: Did you reach out to Philips Electronics, and if so, how?
GetHuman: And which of these common Philips Electronics customer issues best describes the reason you wanted to talk to them?
(Shows ~Fran a list of common Philips Electronics problems)
~Fran: "Complaint" was why I was trying to call.
~Fran's review of Philips Electronics customer service
GetHuman: So how would you sum up your experience for GetHuman's Philips Electronics 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.
~Fran: After waiting though a lot of bad music and repeated messages about "high call volume" (on Sunday afternoon!), finally got a recording they had an "emergency" and to call back some other time. How about never?
GetHuman: Let's quantify your experience contacting Philips Electronics. On a scale of 1 to 5, how easy is it go get help on a Philips Electronics problem?
~Fran: 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?
~Fran: I'd give them a one out of five on communication.
GetHuman: And what about Philips Electronics's ability to quickly and effectively address your problem?
~Fran: For that I would say three out of five.
GetHuman: And finally- any advice for other Philips Electronics customers?
~Fran: Call them early in the day or late. Don't forget any personal or account information you might need for Philips Electronics to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Fran taken from his Philips Electronics customer service problem that occurred on November 11th, 2017.