Harman Kardon: There was zero wait time and mine was a fairly...
A Harman Kardon customer review by GetHuman user GetHuman-308119 from November 21st, 2017
Background on GetHuman-308119's case
GetHuman: GetHuman-308119 - can you tell our other Harman Kardon customers when your case took place?
GetHuman-308119: Yes. It was morning, on November 19th.
GetHuman: Did you reach out to Harman Kardon, and if so, how?
GetHuman: And which of these common Harman Kardon customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-308119 a list of common Harman Kardon problems)
GetHuman-308119: "Returns" was why I was trying to call.
GetHuman-308119's review of Harman Kardon customer service
GetHuman: So how would you sum up your experience for GetHuman's Harman Kardon 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-308119: There was zero wait time and mine was a fairly simple problem to fix thankfully, so the technician patiently walked me through it and everything worked fine thereafter. Thumbs up here :)
GetHuman: Let's quantify your experience contacting Harman Kardon. On a scale of 1 to 5, how easy is it go get help on a Harman Kardon problem?
GetHuman-308119: 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?
GetHuman-308119: I'd give them a two out of five on communication.
GetHuman: And what about Harman Kardon's ability to quickly and effectively address your problem?
GetHuman-308119: For that I would say one out of five.
GetHuman: And finally- any advice for other Harman Kardon customers?
GetHuman-308119: Call them early in the day or late. Don't forget any personal or account information you might need for Harman Kardon to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-308119 taken from his Harman Kardon customer service problem that occurred on November 19th, 2017.