Bright House Networks: Good call. Only problem was I was put on hold f...
A Bright House Networks customer review by GetHuman user ~cabice89 from November 22nd, 2017
Background on ~cabice89's case
GetHuman: ~cabice89 - can you tell our other Bright House Networks customers when your case took place?
~cabice89: Yes I can. It was afternoon, on November 19th.
GetHuman: Did you reach out to Bright House Networks, and if so, how?
GetHuman: And which of these common Bright House Networks customer issues best describes the reason you wanted to talk to them?
(Shows ~cabice89 a list of common Bright House Networks problems)
~cabice89: "Setup service" was why I was trying to call.
~cabice89's review of Bright House Networks customer service
GetHuman: So how would you sum up your experience for GetHuman's Bright House Networks 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.
~cabice89: Good call. Only problem was I was put on hold for * minutes because I was a security system customer as well to cancel a sports pack.
GetHuman: Let's quantify your experience contacting Bright House Networks. On a scale of 1 to 5, how easy is it go get help on a Bright House Networks problem?
~cabice89: I'd give them a one 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?
~cabice89: I'd give them a three out of five on communication.
GetHuman: And what about Bright House Networks's ability to quickly and effectively address your problem?
~cabice89: For that I would say one out of five.
GetHuman: And finally- any advice for other Bright House Networks customers?
~cabice89: Call them early in the day or late. Don't forget any personal or account information you might need for Bright House Networks to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~cabice89 taken from his Bright House Networks customer service problem that occurred on November 19th, 2017.