CMFG Life Insurance: Very Happy I finally called. I've been putting...
A CMFG Life Insurance customer review by GetHuman user ~Ms. Halo from November 26th, 2017
Background on ~Ms. Halo's case
GetHuman: ~Ms. Halo - can you tell our other CMFG Life Insurance customers when your case took place?
~Ms. Halo: Yup. It was afternoon, on November 22nd.
GetHuman: Did you reach out to CMFG Life Insurance, and if so, how?
GetHuman: And which of these common CMFG Life Insurance customer issues best describes the reason you wanted to talk to them?
(Shows ~Ms. Halo a list of common CMFG Life Insurance problems)
~Ms. Halo: "Question" was why I was trying to call.
~Ms. Halo's review of CMFG Life Insurance customer service
GetHuman: So how would you sum up your experience for GetHuman's CMFG Life Insurance 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.
~Ms. Halo: Very Happy I finally called. I've been putting it off for so long. That this was not painful at all and customer service rep. Was very helpful and professional.
GetHuman: Let's quantify your experience contacting CMFG Life Insurance. On a scale of 1 to 5, how easy is it go get help on a CMFG Life Insurance problem?
~Ms. Halo: I'd give them a five 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?
~Ms. Halo: I'd give them a five out of five on communication.
GetHuman: And what about CMFG Life Insurance's ability to quickly and effectively address your problem?
~Ms. Halo: For that I would say three out of five.
GetHuman: And finally- any advice for other CMFG Life Insurance customers?
~Ms. Halo: Call them early in the day or late. Don't forget any personal or account information you might need for CMFG Life Insurance to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Ms. Halo taken from his CMFG Life Insurance customer service problem that occurred on November 22nd, 2017.