Rogers Cable: Got to a service rep with a thick indian accent...
A Rogers Cable customer review by GetHuman user GetHuman-179815 from October 31st, 2017
Background on GetHuman-179815's case
GetHuman: GetHuman-179815 - can you tell our other Rogers Cable customers when your case took place?
GetHuman-179815: Yes I can. It was late at night, on October 29th.
GetHuman: Did you reach out to Rogers Cable, and if so, how?
GetHuman: And which of these common Rogers Cable customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-179815 a list of common Rogers Cable problems)
GetHuman-179815: "I'm moving" was why I was trying to call.
GetHuman-179815's review of Rogers Cable customer service
GetHuman: So how would you sum up your experience for GetHuman's Rogers Cable 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-179815: Got to a service rep with a thick indian accent, and was told i was being transferred after i had called peviously and was on hold fot roughly ** minutes.... not impressed.
GetHuman: Let's quantify your experience contacting Rogers Cable. On a scale of 1 to 5, how easy is it go get help on a Rogers Cable problem?
GetHuman-179815: 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-179815: I'd give them a five out of five on communication.
GetHuman: And what about Rogers Cable's ability to quickly and effectively address your problem?
GetHuman-179815: For that I would say two out of five.
GetHuman: And finally- any advice for other Rogers Cable customers?
GetHuman-179815: Call them early in the day or late. Don't forget any personal or account information you might need for Rogers Cable to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-179815 taken from his Rogers Cable customer service problem that occurred on October 29th, 2017.