Globe Life Insurance: I was approved but was asked to sign the Globe...
A Globe Life Insurance customer review by GetHuman user ~Ken from November 12th, 2017
Background on ~Ken's case
GetHuman: ~Ken - can you tell our other Globe Life Insurance customers when your case took place?
~Ken: Yup. It was middle of the night, on November 9th.
GetHuman: Did you reach out to Globe Life Insurance, and if so, how?
GetHuman: And which of these common Globe Life Insurance customer issues best describes the reason you wanted to talk to them?
(Shows ~Ken a list of common Globe Life Insurance problems)
~Ken: "Lower my rate" was why I was trying to call.
~Ken's review of Globe Life Insurance customer service
GetHuman: So how would you sum up your experience for GetHuman's Globe 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.
~Ken: I was approved but was asked to sign the Globe generated application which gave different answers than I provided on the written application. This would cause real issues if a claim was made by my family.
GetHuman: Let's quantify your experience contacting Globe Life Insurance. On a scale of 1 to 5, how easy is it go get help on a Globe Life Insurance problem?
~Ken: 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?
~Ken: I'd give them a five out of five on communication.
GetHuman: And what about Globe Life Insurance's ability to quickly and effectively address your problem?
~Ken: For that I would say two out of five.
GetHuman: And finally- any advice for other Globe Life Insurance customers?
~Ken: Call them early in the day or late. Don't forget any personal or account information you might need for Globe Life Insurance to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Ken taken from his Globe Life Insurance customer service problem that occurred on November 9th, 2017.