Independence Blue Cross: I ordered replacement for my card and it did no...
A Independence Blue Cross customer review by GetHuman user ~Lena from November 22nd, 2017
Background on ~Lena's case
GetHuman: ~Lena - can you tell our other Independence Blue Cross customers when your case took place?
~Lena: Yeah. It was middle of the night, on November 16th.
GetHuman: Did you reach out to Independence Blue Cross, and if so, how?
GetHuman: And which of these common Independence Blue Cross customer issues best describes the reason you wanted to talk to them?
(Shows ~Lena a list of common Independence Blue Cross problems)
~Lena: "Make/Chase a claim" was why I was trying to call.
~Lena's review of Independence Blue Cross customer service
GetHuman: So how would you sum up your experience for GetHuman's Independence Blue Cross 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.
~Lena: I ordered replacement for my card and it did not arrive. This time person helped me to print temporary card on line while I am waiting for replacement.
GetHuman: Let's quantify your experience contacting Independence Blue Cross. On a scale of 1 to 5, how easy is it go get help on a Independence Blue Cross problem?
~Lena: 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?
~Lena: I'd give them a one out of five on communication.
GetHuman: And what about Independence Blue Cross's ability to quickly and effectively address your problem?
~Lena: For that I would say two out of five.
GetHuman: And finally- any advice for other Independence Blue Cross customers?
~Lena: Call them early in the day or late. Don't forget any personal or account information you might need for Independence Blue Cross to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Lena taken from his Independence Blue Cross customer service problem that occurred on November 16th, 2017.