Apria Healthcare: Incompetent. Inconsiderate. Inept. Uncaring. Ar...
A Apria Healthcare customer review by GetHuman user ~RJC from November 28th, 2017
Background on ~RJC's case
GetHuman: ~RJC - can you tell our other Apria Healthcare customers when your case took place?
~RJC: Yup. It was late at night, on November 20th.
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 ~RJC a list of common Apria Healthcare problems)
~RJC: "Make/Chase a claim" was why I was trying to call.
~RJC'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.
~RJC: Incompetent. Inconsiderate. Inept. Uncaring. Argumentative. Uninformative. Both refill orders have been incorrect. Delivery driver had no idea what he should have delivered. Fortunately he had what was needed but * of ** tanks received were empty on delivery.
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?
~RJC: I'd give them a one 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?
~RJC: I'd give them a three out of five on communication.
GetHuman: And what about Apria Healthcare's ability to quickly and effectively address your problem?
~RJC: For that I would say four out of five.
GetHuman: And finally- any advice for other Apria Healthcare customers?
~RJC: 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 ~RJC taken from his Apria Healthcare customer service problem that occurred on November 20th, 2017.