Bresnan Communications: Great service!
A Bresnan Communications customer review by GetHuman user GetHuman-21729 from November 16th, 2017
Background on GetHuman-21729's case
GetHuman: GetHuman-21729 - can you tell our other Bresnan Communications customers when your case took place?
GetHuman-21729: Yes. It was afternoon, on November 8th.
GetHuman: Did you reach out to Bresnan Communications, and if so, how?
GetHuman: And which of these common Bresnan Communications customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-21729 a list of common Bresnan Communications problems)
GetHuman-21729: "None of those really matches why I wanted to call Bresnan Communications that day." was why I was trying to call.
GetHuman-21729's review of Bresnan Communications customer service
GetHuman: So how would you sum up your experience for GetHuman's Bresnan Communications 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-21729: Great service!
GetHuman: Let's quantify your experience contacting Bresnan Communications. On a scale of 1 to 5, how easy is it go get help on a Bresnan Communications problem?
GetHuman-21729: 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-21729: I'd give them a one out of five on communication.
GetHuman: And what about Bresnan Communications's ability to quickly and effectively address your problem?
GetHuman-21729: For that I would say two out of five.
GetHuman: And finally- any advice for other Bresnan Communications customers?
GetHuman-21729: Call them early in the day or late. Don't forget any personal or account information you might need for Bresnan Communications to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-21729 taken from his Bresnan Communications customer service problem that occurred on November 8th, 2017.