Roku: Terrible. I am going back to Time Warner. For a...
A Roku customer review by GetHuman user ~Lawrence Brenner from November 22nd, 2017
Background on ~Lawrence Brenner's case
GetHuman: ~Lawrence Brenner - can you tell our other Roku customers when your case took place?
~Lawrence Brenner: Yes. It was afternoon, on November 17th.
GetHuman: Did you reach out to Roku, and if so, how?
GetHuman: And which of these common Roku customer issues best describes the reason you wanted to talk to them?
(Shows ~Lawrence Brenner a list of common Roku problems)
~Lawrence Brenner: "Returns" was why I was trying to call.
~Lawrence Brenner's review of Roku customer service
GetHuman: So how would you sum up your experience for GetHuman's Roku 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.
~Lawrence Brenner: Terrible. I am going back to Time Warner. For an hour the voice message was I needed to wait for ** minutes. There was no response. The live chat was worse. I was listed as number ** on the wait list with a ** minutes wait. It never changed and no one responded.
GetHuman: Let's quantify your experience contacting Roku. On a scale of 1 to 5, how easy is it go get help on a Roku problem?
~Lawrence Brenner: 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?
~Lawrence Brenner: I'd give them a three out of five on communication.
GetHuman: And what about Roku's ability to quickly and effectively address your problem?
~Lawrence Brenner: For that I would say two out of five.
GetHuman: And finally- any advice for other Roku customers?
~Lawrence Brenner: Call them early in the day or late. Don't forget any personal or account information you might need for Roku to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Lawrence Brenner taken from his Roku customer service problem that occurred on November 17th, 2017.