RCN simply will not talk to you until you spend...
A RCN customer review by GetHuman user GetHuman-321903 from November 9th, 2017
Background on GetHuman-321903's case
GetHuman: GetHuman-321903 - can you tell our other RCN customers when your case took place?
GetHuman-321903: Yup. It was evening, on November 7th.
GetHuman: Did you reach out to RCN, and if so, how?
GetHuman: And which of these common RCN customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-321903 a list of common RCN problems)
GetHuman-321903: "No service" was why I was trying to call.
GetHuman-321903's review of RCN customer service
GetHuman: So how would you sum up your experience for GetHuman's RCN 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-321903: RCN simply will not talk to you until you spend a vast amount of time filling in all the details that they demand. I waited ** minutes, never got anyone, gave up, tried again at a new number and got back to the same menu,and gave up again. I will try Comcast. RCN clearly has no interest in my business.
GetHuman: Let's quantify your experience contacting RCN. On a scale of 1 to 5, how easy is it go get help on a RCN problem?
GetHuman-321903: 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?
GetHuman-321903: I'd give them a four out of five on communication.
GetHuman: And what about RCN's ability to quickly and effectively address your problem?
GetHuman-321903: For that I would say three out of five.
GetHuman: And finally- any advice for other RCN customers?
GetHuman-321903: Call them early in the day or late. Don't forget any personal or account information you might need for RCN to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-321903 taken from his RCN customer service problem that occurred on November 7th, 2017.