Express Scripts: My first attempt someone picked up the line but...
A Express Scripts customer review by GetHuman user ~GL from November 17th, 2017
Background on ~GL's case
GetHuman: ~GL - can you tell our other Express Scripts customers when your case took place?
~GL: Yup. It was evening, on November 10th.
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 ~GL a list of common Express Scripts problems)
~GL: "Complaint" was why I was trying to call.
~GL'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.
~GL: My first attempt someone picked up the line but did not answer. I heard someone's cell phone receive a text in the background so I knew someone was there. I said hello several times with no response so I decided to hang up and try again. The second time I managed to get someone after being on hold for over ** minutes.
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?
~GL: 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?
~GL: 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?
~GL: For that I would say two out of five.
GetHuman: And finally- any advice for other Express Scripts customers?
~GL: 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 ~GL taken from his Express Scripts customer service problem that occurred on November 10th, 2017.