Panasonic: Absolute worst service in the world. If you do...
Eine Panasonic Kundenbewertung durch GetHuman-Benutzer ~sheyne von November 27., 2017
Background on ~sheyne's case
GetHuman: ~sheyne - can you tell our other Panasonic customers when your case took place?
~sheyne: Yeah. It was middle of the night, on November 18..
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 ~sheyne a list of common Panasonic problems)
~sheyne: "Return an Order" was why I was trying to call.
~sheyne'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.
~sheyne: Absolute worst service in the world. If you don't know to hit zero in response to the voice mail prompts, you have to scream into the phone "yes" or "no" and it just keeps coming back no matter what you do and says "I'm sorry" and then repeats the question. Enough to give one ulcers.
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?
~sheyne: I'd give them a two 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?
~sheyne: I'd give them a five out of five on communication.
GetHuman: And what about Panasonic's ability to quickly and effectively address your problem?
~sheyne: For that I would say four out of five.
GetHuman: And finally- any advice for other Panasonic customers?
~sheyne: Rufen Sie sie früh am Tag oder spät an. Vergessen Sie nicht alle persönlichen oder Kontoinformationen, die Sie benötigen, damit Panasonic weiß, wer Sie sind.
GetHuman: Well there you have it. Some useful feedback and words from ~sheyne taken from his Panasonic customer service problem that occurred on November 18., 2017.