CuraScript: Customer service respresentatives unfamiliar wi...
A CuraScript customer review by GetHuman user ~dynamo30 from November 3rd, 2017
Background on ~dynamo30's case
GetHuman: ~dynamo30 - can you tell our other CuraScript customers when your case took place?
~dynamo30: Sure. It was middle of the night, on November 2nd.
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 ~dynamo30 a list of common CuraScript problems)
~dynamo30: "Make an order" was why I was trying to call.
~dynamo30'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.
~dynamo30: Customer service respresentatives unfamiliar with the medication and very hesitant in responding. Tried to charge me twice when they did not send me enough the *st time. Still on hold as representative unsure about everything!!!! I need these medications to survive!
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?
~dynamo30: 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?
~dynamo30: 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?
~dynamo30: For that I would say one out of five.
GetHuman: And finally- any advice for other CuraScript customers?
~dynamo30: 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 ~dynamo30 taken from his CuraScript customer service problem that occurred on November 2nd, 2017.