Plantronics: Good, but did not have enough technical experti...
A Plantronics customer review by GetHuman user ~WillR from November 27th, 2017
Background on ~WillR's case
GetHuman: ~WillR - can you tell our other Plantronics customers when your case took place?
~WillR: Yup. It was middle of the night, on November 17th.
GetHuman: Did you reach out to Plantronics, and if so, how?
GetHuman: And which of these common Plantronics customer issues best describes the reason you wanted to talk to them?
(Shows ~WillR a list of common Plantronics problems)
~WillR: "Repairs" was why I was trying to call.
~WillR's review of Plantronics customer service
GetHuman: So how would you sum up your experience for GetHuman's Plantronics 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.
~WillR: Good, but did not have enough technical expertise to solve the problem. I did have to wait about ** minutes and wasn't given an ETA, so nearly gave up! Eventually, a chat rep answered and she said that she will get back to me in a few days' time to "ask a higher tier about this issue" by email, which I accepted.
GetHuman: Let's quantify your experience contacting Plantronics. On a scale of 1 to 5, how easy is it go get help on a Plantronics problem?
~WillR: I'd give them a five 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?
~WillR: I'd give them a five out of five on communication.
GetHuman: And what about Plantronics's ability to quickly and effectively address your problem?
~WillR: For that I would say five out of five.
GetHuman: And finally- any advice for other Plantronics customers?
~WillR: Call them early in the day or late. Don't forget any personal or account information you might need for Plantronics to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~WillR taken from his Plantronics customer service problem that occurred on November 17th, 2017.