RCN: Hung up after *** minutes on the second call. F...
A RCN customer review by GetHuman user ~jack collins from November 20th, 2017
Background on ~jack collins's case
GetHuman: ~jack collins - can you tell our other RCN customers when your case took place?
~jack collins: Yeah. It was evening, on November 14th.
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 ~jack collins a list of common RCN problems)
~jack collins: "Billing/Payments" was why I was trying to call.
~jack collins'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.
~jack collins: Hung up after *** minutes on the second call. First call, did not time,hung up. On my *rd call now, at * minutes and holding. Absolutely horrible customer service.To start with, my "sign up" rep lied to me, then stopped taking my calls. Am looking to stop service and go with someone else. HORRIBLE! WISH I NEVER WENT WITH RCN!
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?
~jack collins: I'd give them a three 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?
~jack collins: 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?
~jack collins: For that I would say three out of five.
GetHuman: And finally- any advice for other RCN customers?
~jack collins: 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 ~jack collins taken from his RCN customer service problem that occurred on November 14th, 2017.