Blue Shield (CA): Need more English speakers without fake America...
A Blue Shield (CA) customer review by GetHuman user ~Anonymous from November 18th, 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other Blue Shield (CA) customers when your case took place?
~Anonymous: Yup. It was morning, on November 16th.
GetHuman: Did you reach out to Blue Shield (CA), and if so, how?
GetHuman: And which of these common Blue Shield (CA) customer issues best describes the reason you wanted to talk to them?
(Shows ~Anonymous a list of common Blue Shield (CA) problems)
~Anonymous: "Overcharge/Strange charge" was why I was trying to call.
~Anonymous's review of Blue Shield (CA) customer service
GetHuman: So how would you sum up your experience for GetHuman's Blue Shield (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.
~Anonymous: Need more English speakers without fake American names to help people out trying to do their jobs. My time was wasted and it seemed that she couldn't navigate her system very well.
GetHuman: Let's quantify your experience contacting Blue Shield (CA). On a scale of 1 to 5, how easy is it go get help on a Blue Shield (CA) problem?
~Anonymous: I'd give them a four 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?
~Anonymous: I'd give them a three out of five on communication.
GetHuman: And what about Blue Shield (CA)'s ability to quickly and effectively address your problem?
~Anonymous: For that I would say five out of five.
GetHuman: And finally- any advice for other Blue Shield (CA) customers?
~Anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Blue Shield (CA) to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Anonymous taken from his Blue Shield (CA) customer service problem that occurred on November 16th, 2017.