Roku: I hate my Rocky player it keeps going blank I c...
A Roku customer review by GetHuman user GetHuman-403359 from November 27th, 2017
Background on GetHuman-403359's case
GetHuman: GetHuman-403359 - can you tell our other Roku customers when your case took place?
GetHuman-403359: Yes. It was morning, on November 18th.
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-403359 a list of common Roku problems)
GetHuman-403359: "Device Support" was why I was trying to call.
GetHuman-403359'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-403359: I hate my Rocky player it keeps going blank I called Roky*but the problem is not fixed I'll have to find another way to get netflix on my tv and having to pay **.** for costumer service your warranty expired costumer service shouldn't cost anything. They want you to buy their product
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-403359: 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-403359: 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?
GetHuman-403359: For that I would say two out of five.
GetHuman: And finally- any advice for other Roku customers?
GetHuman-403359: 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-403359 taken from his Roku customer service problem that occurred on November 18th, 2017.