Express Scripts: This is the *th time we've contacted ExpressScr...
A Express Scripts customer review by GetHuman user GetHuman-372754 from November 23rd, 2017
Background on GetHuman-372754's case
GetHuman: GetHuman-372754 - can you tell our other Express Scripts customers when your case took place?
GetHuman-372754: Yes. It was middle of the night, on November 15th.
GetHuman: Did you reach out to Express Scripts, and if so, how?
GetHuman: And which of these common Express Scripts customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-372754 a list of common Express Scripts problems)
GetHuman-372754: "Sign up for service" was why I was trying to call.
GetHuman-372754's review of Express Scripts customer service
GetHuman: So how would you sum up your experience for GetHuman's Express Scripts 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.
GetHuman-372754: This is the *th time we've contacted ExpressScripts to get the Rx refilled. Very time consuming, and not satisfying! At ALL!
GetHuman: Let's quantify your experience contacting Express Scripts. On a scale of 1 to 5, how easy is it go get help on a Express Scripts problem?
GetHuman-372754: I'd give them a four 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?
GetHuman-372754: I'd give them a five out of five on communication.
GetHuman: And what about Express Scripts's ability to quickly and effectively address your problem?
GetHuman-372754: For that I would say four out of five.
GetHuman: And finally- any advice for other Express Scripts customers?
GetHuman-372754: Call them early in the day or late. Don't forget any personal or account information you might need for Express Scripts to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-372754 taken from his Express Scripts customer service problem that occurred on November 15th, 2017.