Panasonic: I understood the voice on the phone , but I nev...
A Panasonic customer review by GetHuman user GetHuman-432597 from November 18th, 2017
Background on GetHuman-432597's case
GetHuman: GetHuman-432597 - can you tell our other Panasonic customers when your case took place?
GetHuman-432597: Yeah. It was morning, on November 10th.
GetHuman: Did you reach out to Panasonic, and if so, how?
GetHuman: And which of these common Panasonic customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-432597 a list of common Panasonic problems)
GetHuman-432597: "Returns" was why I was trying to call.
GetHuman-432597's review of Panasonic customer service
GetHuman: So how would you sum up your experience for GetHuman's Panasonic 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-432597: I understood the voice on the phone , but I never got to talk to a live person to help me. This is the worst service I've ever talked to and I have talked to some bad ones before. They need a live person to help people
GetHuman: Let's quantify your experience contacting Panasonic. On a scale of 1 to 5, how easy is it go get help on a Panasonic problem?
GetHuman-432597: 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?
GetHuman-432597: I'd give them a one out of five on communication.
GetHuman: And what about Panasonic's ability to quickly and effectively address your problem?
GetHuman-432597: For that I would say four out of five.
GetHuman: And finally- any advice for other Panasonic customers?
GetHuman-432597: Call them early in the day or late. Don't forget any personal or account information you might need for Panasonic to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-432597 taken from his Panasonic customer service problem that occurred on November 10th, 2017.