Covered California: Worker: Krishna then Heather both refused to t...
A Covered California customer review by GetHuman user ~gotohell! from November 25th, 2017
Background on ~gotohell!'s case
GetHuman: ~gotohell! - can you tell our other Covered California customers when your case took place?
~gotohell!: Yes. It was evening, on November 20th.
GetHuman: Did you reach out to Covered California, and if so, how?
GetHuman: And which of these common Covered California customer issues best describes the reason you wanted to talk to them?
(Shows ~gotohell! a list of common Covered California problems)
~gotohell!: "Question" was why I was trying to call.
~gotohell!'s review of Covered California customer service
GetHuman: So how would you sum up your experience for GetHuman's Covered California 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.
~gotohell!: Worker: Krishna then Heather both refused to transfer my call to a supervisor when they were unable to help. Krishna in particular was extremely rude and hung up on me.
GetHuman: Let's quantify your experience contacting Covered California. On a scale of 1 to 5, how easy is it go get help on a Covered California problem?
~gotohell!: 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?
~gotohell!: I'd give them a two out of five on communication.
GetHuman: And what about Covered California's ability to quickly and effectively address your problem?
~gotohell!: For that I would say five out of five.
GetHuman: And finally- any advice for other Covered California customers?
~gotohell!: Call them early in the day or late. Don't forget any personal or account information you might need for Covered California to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~gotohell! taken from his Covered California customer service problem that occurred on November 20th, 2017.