UMR Health Benefits: waited ** minutes and when I finally got to som...
A UMR Health Benefits customer review by GetHuman user ~aaocc from November 25th, 2017
Background on ~aaocc's case
GetHuman: ~aaocc - can you tell our other UMR Health Benefits customers when your case took place?
~aaocc: Sure. It was morning, on November 24th.
GetHuman: Did you reach out to UMR Health Benefits, and if so, how?
GetHuman: And which of these common UMR Health Benefits customer issues best describes the reason you wanted to talk to them?
(Shows ~aaocc a list of common UMR Health Benefits problems)
~aaocc: "Renew coverage" was why I was trying to call.
~aaocc's review of UMR Health Benefits customer service
GetHuman: So how would you sum up your experience for GetHuman's UMR Health Benefits 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.
~aaocc: waited ** minutes and when I finally got to someone they could not answer simple benefits questions and transferred me back to the "provider relations" automated line that does not lead to any human. hahaha
GetHuman: Let's quantify your experience contacting UMR Health Benefits. On a scale of 1 to 5, how easy is it go get help on a UMR Health Benefits problem?
~aaocc: 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?
~aaocc: I'd give them a three out of five on communication.
GetHuman: And what about UMR Health Benefits's ability to quickly and effectively address your problem?
~aaocc: For that I would say one out of five.
GetHuman: And finally- any advice for other UMR Health Benefits customers?
~aaocc: Call them early in the day or late. Don't forget any personal or account information you might need for UMR Health Benefits to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~aaocc taken from his UMR Health Benefits customer service problem that occurred on November 24th, 2017.