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