United Healthcare: I needed the information for my indemnity plan...
A United Healthcare customer review by GetHuman user GetHuman-77647 from November 25th, 2017
Background on GetHuman-77647's case
GetHuman: GetHuman-77647 - can you tell our other United Healthcare customers when your case took place?
GetHuman-77647: Yeah. It was morning, on November 23rd.
GetHuman: Did you reach out to United Healthcare, and if so, how?
GetHuman: And which of these common United Healthcare customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-77647 a list of common United Healthcare problems)
GetHuman-77647: "Overcharge on Account" was why I was trying to call.
GetHuman-77647's review of United Healthcare customer service
GetHuman: So how would you sum up your experience for GetHuman's United Healthcare 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.
GetHuman-77647: I needed the information for my indemnity plan through AARP. I was redirected * times and was on hold *** each time
GetHuman: Let's quantify your experience contacting United Healthcare. On a scale of 1 to 5, how easy is it go get help on a United Healthcare problem?
GetHuman-77647: I'd give them a five 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?
GetHuman-77647: I'd give them a four out of five on communication.
GetHuman: And what about United Healthcare's ability to quickly and effectively address your problem?
GetHuman-77647: For that I would say three out of five.
GetHuman: And finally- any advice for other United Healthcare customers?
GetHuman-77647: Call them early in the day or late. Don't forget any personal or account information you might need for United Healthcare to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-77647 taken from his United Healthcare customer service problem that occurred on November 23rd, 2017.