Right Source RX: They had a phone number for me that was ** year...
A Right Source RX customer review by GetHuman user ~Pam from November 19th, 2017
Background on ~Pam's case
GetHuman: ~Pam - can you tell our other Right Source RX customers when your case took place?
~Pam: Yeah. It was afternoon, on November 10th.
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 ~Pam a list of common Right Source RX problems)
~Pam: "Product information" was why I was trying to call.
~Pam'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.
~Pam: They had a phone number for me that was ** years old, in spite of my recent application. I was disconnected from the person I spoke with and she never called back. I tried calling her but was told I could not request any certain rep. Walgreens is so much easier to deal with.
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?
~Pam: 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?
~Pam: I'd give them a three out of five on communication.
GetHuman: And what about Right Source RX's ability to quickly and effectively address your problem?
~Pam: For that I would say five out of five.
GetHuman: And finally- any advice for other Right Source RX customers?
~Pam: 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 ~Pam taken from his Right Source RX customer service problem that occurred on November 10th, 2017.