Roku: Obviously connecting to India could barely unde...
A Roku customer review by GetHuman user ~anonymous from November 8th, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other Roku customers when your case took place?
~anonymous: Sure. It was evening, on November 5th.
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 ~anonymous a list of common Roku problems)
~anonymous: "Refund a Charge" was why I was trying to call.
~anonymous'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.
~anonymous: Obviously connecting to India could barely understand them. Buyer beware they offer free ** day technical support (if you can understand them) after that they want your credit card number and try to sell you tech suppport "programs". They also offer a live chat option on their website which I tried four times I was number **, **. **, and ** in queue. Just pathetic.
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?
~anonymous: 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?
~anonymous: 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?
~anonymous: For that I would say two out of five.
GetHuman: And finally- any advice for other Roku customers?
~anonymous: 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 ~anonymous taken from his Roku customer service problem that occurred on November 5th, 2017.