Roku: Talked with a very nice lady from India. I unde...
A Roku customer review by GetHuman user GetHuman-183287 from November 18th, 2017
Background on GetHuman-183287's case
GetHuman: GetHuman-183287 - can you tell our other Roku customers when your case took place?
GetHuman-183287: Yeah. It was morning, on November 12th.
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 GetHuman-183287 a list of common Roku problems)
GetHuman-183287: "Returns" was why I was trying to call.
GetHuman-183287'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.
GetHuman-183287: Talked with a very nice lady from India. I understood her perfectly! SO much better than the woman I spoke with about my aol account!! I think maybe some of you may have selective hearing. From my experiences, people from India use excellent grammar while people in the US can't even spell!!
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?
GetHuman-183287: 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?
GetHuman-183287: I'd give them a five out of five on communication.
GetHuman: And what about Roku's ability to quickly and effectively address your problem?
GetHuman-183287: For that I would say two out of five.
GetHuman: And finally- any advice for other Roku customers?
GetHuman-183287: 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 GetHuman-183287 taken from his Roku customer service problem that occurred on November 12th, 2017.