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