Comptroller of Maryland: Constantly unable to reach a representative. Ca...
A Comptroller of Maryland customer review by GetHuman user ~Ty from November 23rd, 2017
Background on ~Ty's case
GetHuman: ~Ty - can you tell our other Comptroller of Maryland customers when your case took place?
~Ty: Yeah. It was evening, on November 16th.
GetHuman: Did you reach out to Comptroller of Maryland, and if so, how?
GetHuman: And which of these common Comptroller of Maryland customer issues best describes the reason you wanted to talk to them?
(Shows ~Ty a list of common Comptroller of Maryland problems)
~Ty: "Local services" was why I was trying to call.
~Ty's review of Comptroller of Maryland customer service
GetHuman: So how would you sum up your experience for GetHuman's Comptroller of Maryland 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.
~Ty: Constantly unable to reach a representative. Call is disconnected constantly before I can ever speak to someone and no one has to replied to my e-mail about this problem.
GetHuman: Let's quantify your experience contacting Comptroller of Maryland. On a scale of 1 to 5, how easy is it go get help on a Comptroller of Maryland problem?
~Ty: 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?
~Ty: I'd give them a five out of five on communication.
GetHuman: And what about Comptroller of Maryland's ability to quickly and effectively address your problem?
~Ty: For that I would say three out of five.
GetHuman: And finally- any advice for other Comptroller of Maryland customers?
~Ty: Call them early in the day or late. Don't forget any personal or account information you might need for Comptroller of Maryland to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Ty taken from his Comptroller of Maryland customer service problem that occurred on November 16th, 2017.