Express Scripts: Spoke with Michael who could not have been more...
A Express Scripts customer review by GetHuman user GetHuman-232651 from November 14th, 2017
Background on GetHuman-232651's case
GetHuman: GetHuman-232651 - can you tell our other Express Scripts customers when your case took place?
GetHuman-232651: Sure. It was afternoon, on November 4th.
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-232651 a list of common Express Scripts problems)
GetHuman-232651: "Recover Account" was why I was trying to call.
GetHuman-232651'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-232651: Spoke with Michael who could not have been more helpful. Answered all my questions completely ad volunteered information I might need in the future.
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-232651: I'd give them a five 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-232651: 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-232651: For that I would say one out of five.
GetHuman: And finally- any advice for other Express Scripts customers?
GetHuman-232651: 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-232651 taken from his Express Scripts customer service problem that occurred on November 4th, 2017.