CareFirst: ** minute wait time reported when calling in at...
A CareFirst customer review by GetHuman user GetHuman-226768 from November 17th, 2017
Background on GetHuman-226768's case
GetHuman: GetHuman-226768 - can you tell our other CareFirst customers when your case took place?
GetHuman-226768: Yup. It was middle of the night, on November 10th.
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-226768 a list of common CareFirst problems)
GetHuman-226768: "Update account information" was why I was trying to call.
GetHuman-226768'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-226768: ** minute wait time reported when calling in at **:** AM on a Tuesday. BUT they had a feature to let them call me back when my place in line came. So assuming that actually, happens, it's not as bad as it could be!
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-226768: 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?
GetHuman-226768: I'd give them a one out of five on communication.
GetHuman: And what about CareFirst's ability to quickly and effectively address your problem?
GetHuman-226768: For that I would say four out of five.
GetHuman: And finally- any advice for other CareFirst customers?
GetHuman-226768: 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-226768 taken from his CareFirst customer service problem that occurred on November 10th, 2017.