Right Source RX: I have been trying to get a $**.** billing erro...
A Right Source RX customer review by GetHuman user ~panamint from November 7th, 2017
Background on ~panamint's case
GetHuman: ~panamint - can you tell our other Right Source RX customers when your case took place?
~panamint: Yes. It was afternoon, on October 28th.
GetHuman: Did you reach out to Right Source RX, and if so, how?
GetHuman: And which of these common Right Source RX customer issues best describes the reason you wanted to talk to them?
(Shows ~panamint a list of common Right Source RX problems)
~panamint: "Returns" was why I was trying to call.
~panamint's review of Right Source RX customer service
GetHuman: So how would you sum up your experience for GetHuman's Right Source RX 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.
~panamint: I have been trying to get a $**.** billing error that they over charged me straightened out for over three month. Every person you talk to tells you something else and lie to you. They are so dumb that they can,t do basic math.
GetHuman: Let's quantify your experience contacting Right Source RX. On a scale of 1 to 5, how easy is it go get help on a Right Source RX problem?
~panamint: 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?
~panamint: I'd give them a five out of five on communication.
GetHuman: And what about Right Source RX's ability to quickly and effectively address your problem?
~panamint: For that I would say five out of five.
GetHuman: And finally- any advice for other Right Source RX customers?
~panamint: Call them early in the day or late. Don't forget any personal or account information you might need for Right Source RX to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~panamint taken from his Right Source RX customer service problem that occurred on October 28th, 2017.