CareFirst: I was disconnected while on hold the first time...
A CareFirst customer review by GetHuman user GetHuman-44977 from November 22nd, 2017
Background on GetHuman-44977's case
GetHuman: GetHuman-44977 - can you tell our other CareFirst customers when your case took place?
GetHuman-44977: Yeah. It was middle of the night, on November 18th.
GetHuman: Did you reach out to CareFirst, and if so, how?
GetHuman: And which of these common CareFirst customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-44977 a list of common CareFirst problems)
GetHuman-44977: "Get insurance" was why I was trying to call.
GetHuman-44977's review of CareFirst customer service
GetHuman: So how would you sum up your experience for GetHuman's CareFirst 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.
GetHuman-44977: I was disconnected while on hold the first time, but called back and immediately told the voice system "representative". The gentleman I spoke with was very helpful and I wasn't on hold for too long. I called on Wednesday at *PM EST.
GetHuman: Let's quantify your experience contacting CareFirst. On a scale of 1 to 5, how easy is it go get help on a CareFirst problem?
GetHuman-44977: I'd give them a three 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?
GetHuman-44977: I'd give them a two out of five on communication.
GetHuman: And what about CareFirst's ability to quickly and effectively address your problem?
GetHuman-44977: For that I would say one out of five.
GetHuman: And finally- any advice for other CareFirst customers?
GetHuman-44977: Call them early in the day or late. Don't forget any personal or account information you might need for CareFirst to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-44977 taken from his CareFirst customer service problem that occurred on November 18th, 2017.