Blue Cross Blue Shield (MI): Unacceptable wait time to talk to a claims pers...
A Blue Cross Blue Shield (MI) customer review by GetHuman user ~pamlr from November 25th, 2017
Background on ~pamlr's case
GetHuman: ~pamlr - can you tell our other Blue Cross Blue Shield (MI) customers when your case took place?
~pamlr: Yes. It was evening, on November 23rd.
GetHuman: Did you reach out to Blue Cross Blue Shield (MI), and if so, how?
GetHuman: And which of these common Blue Cross Blue Shield (MI) customer issues best describes the reason you wanted to talk to them?
(Shows ~pamlr a list of common Blue Cross Blue Shield (MI) problems)
~pamlr: "Find a provider" was why I was trying to call.
~pamlr's review of Blue Cross Blue Shield (MI) customer service
GetHuman: So how would you sum up your experience for GetHuman's Blue Cross Blue Shield (MI) 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.
~pamlr: Unacceptable wait time to talk to a claims person. My overall call was *.* hours and still not resolve my issue.
GetHuman: Let's quantify your experience contacting Blue Cross Blue Shield (MI). On a scale of 1 to 5, how easy is it go get help on a Blue Cross Blue Shield (MI) problem?
~pamlr: 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?
~pamlr: I'd give them a one out of five on communication.
GetHuman: And what about Blue Cross Blue Shield (MI)'s ability to quickly and effectively address your problem?
~pamlr: For that I would say four out of five.
GetHuman: And finally- any advice for other Blue Cross Blue Shield (MI) customers?
~pamlr: Call them early in the day or late. Don't forget any personal or account information you might need for Blue Cross Blue Shield (MI) to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~pamlr taken from his Blue Cross Blue Shield (MI) customer service problem that occurred on November 23rd, 2017.