UMR Health Benefits: The number was good,but operator sent me to aut...
A UMR Health Benefits customer review by GetHuman user ~xxxx from November 24th, 2017
Background on ~xxxx's case
GetHuman: ~xxxx - can you tell our other UMR Health Benefits customers when your case took place?
~xxxx: Sure. It was evening, on November 22nd.
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 ~xxxx a list of common UMR Health Benefits problems)
~xxxx: "Contact customer support" was why I was trying to call.
~xxxx'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.
~xxxx: The number was good,but operator sent me to automated * times, and the *rd time I called back I was explicit about not sending me to automated and she finally sent me to cliams rep. But it worked.
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?
~xxxx: 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?
~xxxx: 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?
~xxxx: For that I would say four out of five.
GetHuman: And finally- any advice for other UMR Health Benefits customers?
~xxxx: 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 ~xxxx taken from his UMR Health Benefits customer service problem that occurred on November 22nd, 2017.