Blue Cross/Blue Shield (IL): Multiple calls to the number on the back of ID...
A Blue Cross/Blue Shield (IL) customer review by GetHuman user ~MD from November 20th, 2017
Background on ~MD's case
GetHuman: ~MD - can you tell our other Blue Cross/Blue Shield (IL) customers when your case took place?
~MD: Yes. It was middle of the night, on November 17th.
GetHuman: Did you reach out to Blue Cross/Blue Shield (IL), and if so, how?
GetHuman: And which of these common Blue Cross/Blue Shield (IL) customer issues best describes the reason you wanted to talk to them?
(Shows ~MD a list of common Blue Cross/Blue Shield (IL) problems)
~MD: "Billing" was why I was trying to call.
~MD's review of Blue Cross/Blue Shield (IL) customer service
GetHuman: So how would you sum up your experience for GetHuman's Blue Cross/Blue Shield (IL) 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.
~MD: Multiple calls to the number on the back of ID cards with hold times from **-*** minutes and NEVER a resoponse.
GetHuman: Let's quantify your experience contacting Blue Cross/Blue Shield (IL). On a scale of 1 to 5, how easy is it go get help on a Blue Cross/Blue Shield (IL) problem?
~MD: 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?
~MD: I'd give them a three out of five on communication.
GetHuman: And what about Blue Cross/Blue Shield (IL)'s ability to quickly and effectively address your problem?
~MD: For that I would say five out of five.
GetHuman: And finally- any advice for other Blue Cross/Blue Shield (IL) customers?
~MD: Call them early in the day or late. Don't forget any personal or account information you might need for Blue Cross/Blue Shield (IL) to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~MD taken from his Blue Cross/Blue Shield (IL) customer service problem that occurred on November 17th, 2017.