MassHealth: HAHAHA an automated service calls me back? Sho...
A MassHealth customer review by GetHuman user ~junk insurance from November 11th, 2017
Background on ~junk insurance's case
GetHuman: ~junk insurance - can you tell our other MassHealth customers when your case took place?
~junk insurance: Yes I can. It was evening, on November 7th.
GetHuman: Did you reach out to MassHealth, and if so, how?
GetHuman: And which of these common MassHealth customer issues best describes the reason you wanted to talk to them?
(Shows ~junk insurance a list of common MassHealth problems)
~junk insurance: "Get insurance" was why I was trying to call.
~junk insurance's review of MassHealth customer service
GetHuman: So how would you sum up your experience for GetHuman's MassHealth 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.
~junk insurance: HAHAHA an automated service calls me back? Shouldve known that. Is it ever possible to reach a person there? They make it sound like the *** **** number is for vip. Silly me for believing anything masshealth claims.
GetHuman: Let's quantify your experience contacting MassHealth. On a scale of 1 to 5, how easy is it go get help on a MassHealth problem?
~junk insurance: 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?
~junk insurance: I'd give them a three out of five on communication.
GetHuman: And what about MassHealth's ability to quickly and effectively address your problem?
~junk insurance: For that I would say one out of five.
GetHuman: And finally- any advice for other MassHealth customers?
~junk insurance: Call them early in the day or late. Don't forget any personal or account information you might need for MassHealth to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~junk insurance taken from his MassHealth customer service problem that occurred on November 7th, 2017.