I WORK AT MERITAIN HEALTH* IF U PUT THE ID NUMB...
A Meritain Health customer review by GetHuman user GetHuman-308895 from November 22nd, 2017
Background on GetHuman-308895's case
GetHuman: GetHuman-308895 - can you tell our other Meritain Health customers when your case took place?
GetHuman-308895: Yes I can. It was evening, on November 12th.
GetHuman: Did you reach out to Meritain Health, and if so, how?
GetHuman: And which of these common Meritain Health customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-308895 a list of common Meritain Health problems)
GetHuman-308895: "Renew coverage" was why I was trying to call.
GetHuman-308895's review of Meritain Health customer service
GetHuman: So how would you sum up your experience for GetHuman's Meritain Health 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-308895: I WORK AT MERITAIN HEALTH* IF U PUT THE ID NUMBER IN AS REQUESTED UR CALL BE ROUTED TO THE CORRECT CUE* IF U DO NOT YEA U WILL BE HOLDING A LONG TIME
GetHuman: Let's quantify your experience contacting Meritain Health. On a scale of 1 to 5, how easy is it go get help on a Meritain Health problem?
GetHuman-308895: 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-308895: I'd give them a two out of five on communication.
GetHuman: And what about Meritain Health's ability to quickly and effectively address your problem?
GetHuman-308895: For that I would say five out of five.
GetHuman: And finally- any advice for other Meritain Health customers?
GetHuman-308895: Call them early in the day or late. Don't forget any personal or account information you might need for Meritain Health to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-308895 taken from his Meritain Health customer service problem that occurred on November 12th, 2017.