HealthCare.gov: Called twice. On hold * hour each time before...
A HealthCare.gov customer review by GetHuman user GetHuman-187594 from November 20th, 2017
Background on GetHuman-187594's case
GetHuman: GetHuman-187594 - can you tell our other HealthCare.gov customers when your case took place?
GetHuman-187594: Yes. It was evening, on November 13th.
GetHuman: Did you reach out to HealthCare.gov, and if so, how?
GetHuman: And which of these common HealthCare.gov customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-187594 a list of common HealthCare.gov problems)
GetHuman-187594: "Cancel coverage" was why I was trying to call.
GetHuman-187594's review of HealthCare.gov customer service
GetHuman: So how would you sum up your experience for GetHuman's HealthCare.gov 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-187594: Called twice. On hold * hour each time before hanging up. Tried callback feature and computer called my back a day later leaving me a voicemail with the same *** number on it.
GetHuman: Let's quantify your experience contacting HealthCare.gov. On a scale of 1 to 5, how easy is it go get help on a HealthCare.gov problem?
GetHuman-187594: 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?
GetHuman-187594: I'd give them a one out of five on communication.
GetHuman: And what about HealthCare.gov's ability to quickly and effectively address your problem?
GetHuman-187594: For that I would say two out of five.
GetHuman: And finally- any advice for other HealthCare.gov customers?
GetHuman-187594: Call them early in the day or late. Don't forget any personal or account information you might need for HealthCare.gov to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-187594 taken from his HealthCare.gov customer service problem that occurred on November 13th, 2017.