Anthem Blue Cross CA: I dialed the number, got an automatied voice th...
A Anthem Blue Cross CA customer review by GetHuman user ~Spici Jello from November 13th, 2017
Background on ~Spici Jello's case
GetHuman: ~Spici Jello - can you tell our other Anthem Blue Cross CA customers when your case took place?
~Spici Jello: Sure. It was evening, on November 7th.
GetHuman: Did you reach out to Anthem Blue Cross CA, and if so, how?
GetHuman: And which of these common Anthem Blue Cross CA customer issues best describes the reason you wanted to talk to them?
(Shows ~Spici Jello a list of common Anthem Blue Cross CA problems)
~Spici Jello: "Coverage question" was why I was trying to call.
~Spici Jello's review of Anthem Blue Cross CA customer service
GetHuman: So how would you sum up your experience for GetHuman's Anthem Blue Cross CA 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.
~Spici Jello: I dialed the number, got an automatied voice that said "thank you for calling, good bye." and hung up on me
GetHuman: Let's quantify your experience contacting Anthem Blue Cross CA. On a scale of 1 to 5, how easy is it go get help on a Anthem Blue Cross CA problem?
~Spici Jello: 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?
~Spici Jello: I'd give them a one out of five on communication.
GetHuman: And what about Anthem Blue Cross CA's ability to quickly and effectively address your problem?
~Spici Jello: For that I would say one out of five.
GetHuman: And finally- any advice for other Anthem Blue Cross CA customers?
~Spici Jello: Call them early in the day or late. Don't forget any personal or account information you might need for Anthem Blue Cross CA to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Spici Jello taken from his Anthem Blue Cross CA customer service problem that occurred on November 7th, 2017.