Medco Pharmacy: We have had excellent service from Medco, for t...
A Medco Pharmacy customer review by GetHuman user GetHuman-266468 from November 5th, 2017
Background on GetHuman-266468's case
GetHuman: GetHuman-266468 - can you tell our other Medco Pharmacy customers when your case took place?
GetHuman-266468: Yup. It was middle of the night, on November 4th.
GetHuman: Did you reach out to Medco Pharmacy, and if so, how?
GetHuman: And which of these common Medco Pharmacy customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-266468 a list of common Medco Pharmacy problems)
GetHuman-266468: "Complaint" was why I was trying to call.
GetHuman-266468's review of Medco Pharmacy customer service
GetHuman: So how would you sum up your experience for GetHuman's Medco Pharmacy 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-266468: We have had excellent service from Medco, for the most part. A couple of little things here and there were corrected fast. Really like the company.
GetHuman: Let's quantify your experience contacting Medco Pharmacy. On a scale of 1 to 5, how easy is it go get help on a Medco Pharmacy problem?
GetHuman-266468: 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-266468: I'd give them a five out of five on communication.
GetHuman: And what about Medco Pharmacy's ability to quickly and effectively address your problem?
GetHuman-266468: For that I would say five out of five.
GetHuman: And finally- any advice for other Medco Pharmacy customers?
GetHuman-266468: Call them early in the day or late. Don't forget any personal or account information you might need for Medco Pharmacy to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-266468 taken from his Medco Pharmacy customer service problem that occurred on November 4th, 2017.