UMR Health Benefits: Usually I have tons of problems with UMR. But t...
A UMR Health Benefits customer review by GetHuman user ~AC from November 26th, 2017
Background on ~AC's case
GetHuman: ~AC - can you tell our other UMR Health Benefits customers when your case took place?
~AC: Sure. It was middle of the night, on November 20th.
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 ~AC a list of common UMR Health Benefits problems)
~AC: "Billing inquiry" was why I was trying to call.
~AC'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.
~AC: Usually I have tons of problems with UMR. But today I said "operator", and they transferred me to a customer service rep without me even asking. The customer service rep was polite and efficient. Best experience yet with UMR.
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?
~AC: 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?
~AC: I'd give them a one out of five on communication.
GetHuman: And what about UMR Health Benefits's ability to quickly and effectively address your problem?
~AC: For that I would say four out of five.
GetHuman: And finally- any advice for other UMR Health Benefits customers?
~AC: 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 ~AC taken from his UMR Health Benefits customer service problem that occurred on November 20th, 2017.