CuraScript: This has got to be one of the worst pharmacys t...
A CuraScript customer review by GetHuman user ~anonymous from November 19th, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other CuraScript customers when your case took place?
~anonymous: Yeah. It was middle of the night, on November 11th.
GetHuman: Did you reach out to CuraScript, and if so, how?
GetHuman: And which of these common CuraScript customer issues best describes the reason you wanted to talk to them?
(Shows ~anonymous a list of common CuraScript problems)
~anonymous: "Product information" was why I was trying to call.
~anonymous's review of CuraScript customer service
GetHuman: So how would you sum up your experience for GetHuman's CuraScript 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.
~anonymous: This has got to be one of the worst pharmacys to get a script through. I am on a speciality med that keeps brain tumors from growing and after * weeks of back and forth I still do not have my meds. INCOMPETENT is the word that comes to mind for this business.
GetHuman: Let's quantify your experience contacting CuraScript. On a scale of 1 to 5, how easy is it go get help on a CuraScript problem?
~anonymous: 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?
~anonymous: I'd give them a one out of five on communication.
GetHuman: And what about CuraScript's ability to quickly and effectively address your problem?
~anonymous: For that I would say one out of five.
GetHuman: And finally- any advice for other CuraScript customers?
~anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for CuraScript to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~anonymous taken from his CuraScript customer service problem that occurred on November 11th, 2017.