Mutual of Omaha: I am outside the USA. I cannot call during US b...
A Mutual of Omaha customer review by GetHuman user ~HowdyPanda from November 14th, 2017
Background on ~HowdyPanda's case
GetHuman: ~HowdyPanda - can you tell our other Mutual of Omaha customers when your case took place?
~HowdyPanda: Yup. It was afternoon, on November 4th.
GetHuman: Did you reach out to Mutual of Omaha, and if so, how?
GetHuman: And which of these common Mutual of Omaha customer issues best describes the reason you wanted to talk to them?
(Shows ~HowdyPanda a list of common Mutual of Omaha problems)
~HowdyPanda: "Question" was why I was trying to call.
~HowdyPanda's review of Mutual of Omaha customer service
GetHuman: So how would you sum up your experience for GetHuman's Mutual of Omaha 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.
~HowdyPanda: I am outside the USA. I cannot call during US business hours. I only have web access between * *PM & *AM US time. Their phone access is only *-* US time. They have no email address. I CAN'T contact them.
GetHuman: Let's quantify your experience contacting Mutual of Omaha. On a scale of 1 to 5, how easy is it go get help on a Mutual of Omaha problem?
~HowdyPanda: 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?
~HowdyPanda: I'd give them a four out of five on communication.
GetHuman: And what about Mutual of Omaha's ability to quickly and effectively address your problem?
~HowdyPanda: For that I would say one out of five.
GetHuman: And finally- any advice for other Mutual of Omaha customers?
~HowdyPanda: Call them early in the day or late. Don't forget any personal or account information you might need for Mutual of Omaha to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~HowdyPanda taken from his Mutual of Omaha customer service problem that occurred on November 4th, 2017.