MassHealth: waited ** minutes and the computer just cut the...
A MassHealth customer review by GetHuman user ~mariafa from November 27th, 2017
Background on ~mariafa's case
GetHuman: ~mariafa - can you tell our other MassHealth customers when your case took place?
~mariafa: Yes I can. It was evening, on November 25th.
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 ~mariafa a list of common MassHealth problems)
~mariafa: "Make/Chase a claim" was why I was trying to call.
~mariafa'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.
~mariafa: waited ** minutes and the computer just cut the line... called again .. same thing... again got through and person was extremely rude and didnt help me at all... called again on wait another **.. cut again.. wait another ** minutes.. still not answering.. im on hold as i type this
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?
~mariafa: 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?
~mariafa: 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?
~mariafa: For that I would say two out of five.
GetHuman: And finally- any advice for other MassHealth customers?
~mariafa: 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 ~mariafa taken from his MassHealth customer service problem that occurred on November 25th, 2017.