Logitech: trying to replace two defective items, need top...
A Logitech customer review by GetHuman user ~Chris from November 28th, 2017
Background on ~Chris's case
GetHuman: ~Chris - can you tell our other Logitech customers when your case took place?
~Chris: Yup. It was morning, on November 24th.
GetHuman: Did you reach out to Logitech, and if so, how?
GetHuman: And which of these common Logitech customer issues best describes the reason you wanted to talk to them?
(Shows ~Chris a list of common Logitech problems)
~Chris: "Where to buy" was why I was trying to call.
~Chris's review of Logitech customer service
GetHuman: So how would you sum up your experience for GetHuman's Logitech 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.
~Chris: trying to replace two defective items, need top send them to logitech first and wait for new ones to arrive. I use both items for work at home and cannot do that. Asked to speak to a supervisor was told id receive a call within **-** hours. no callback within that timeframe i called on a friday at *pm PST and no supervisor was available and i got disconnected.
GetHuman: Let's quantify your experience contacting Logitech. On a scale of 1 to 5, how easy is it go get help on a Logitech problem?
~Chris: I'd give them a three 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?
~Chris: I'd give them a two out of five on communication.
GetHuman: And what about Logitech's ability to quickly and effectively address your problem?
~Chris: For that I would say three out of five.
GetHuman: And finally- any advice for other Logitech customers?
~Chris: Call them early in the day or late. Don't forget any personal or account information you might need for Logitech to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Chris taken from his Logitech customer service problem that occurred on November 24th, 2017.