Apria Healthcare: I have never dealt with a company such as this...
A Apria Healthcare customer review by GetHuman user ~linda from November 21st, 2017
Background on ~linda's case
GetHuman: ~linda - can you tell our other Apria Healthcare customers when your case took place?
~linda: Sure. It was late at night, on November 19th.
GetHuman: Did you reach out to Apria Healthcare, and if so, how?
GetHuman: And which of these common Apria Healthcare customer issues best describes the reason you wanted to talk to them?
(Shows ~linda a list of common Apria Healthcare problems)
~linda: "Update account information" was why I was trying to call.
~linda's review of Apria Healthcare customer service
GetHuman: So how would you sum up your experience for GetHuman's Apria 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.
~linda: I have never dealt with a company such as this. To say this is a professional company is understatement. I cannot wait for my husband to get a new script so we can change companies. I would NOT recommend this company to anyone.
GetHuman: Let's quantify your experience contacting Apria Healthcare. On a scale of 1 to 5, how easy is it go get help on a Apria Healthcare problem?
~linda: I'd give them a two 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?
~linda: I'd give them a one out of five on communication.
GetHuman: And what about Apria Healthcare's ability to quickly and effectively address your problem?
~linda: For that I would say two out of five.
GetHuman: And finally- any advice for other Apria Healthcare customers?
~linda: Call them early in the day or late. Don't forget any personal or account information you might need for Apria Healthcare to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~linda taken from his Apria Healthcare customer service problem that occurred on November 19th, 2017.