Caremark: This is the *th time this year they have mis re...
A Caremark customer review by GetHuman user ~Discouraged from November 5th, 2017
Background on ~Discouraged's case
GetHuman: ~Discouraged - can you tell our other Caremark customers when your case took place?
~Discouraged: Yeah. It was afternoon, on October 26th.
GetHuman: Did you reach out to Caremark, and if so, how?
GetHuman: And which of these common Caremark customer issues best describes the reason you wanted to talk to them?
(Shows ~Discouraged a list of common Caremark problems)
~Discouraged: "Product information" was why I was trying to call.
~Discouraged's review of Caremark customer service
GetHuman: So how would you sum up your experience for GetHuman's Caremark 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.
~Discouraged: This is the *th time this year they have mis read or not issued or pended by prescriotion. This time they told me the instructions were incomplete and they have been sitting on this since May **. It's June **th now. Excuses excuses excuses It's a company plan and I have no other choice.
GetHuman: Let's quantify your experience contacting Caremark. On a scale of 1 to 5, how easy is it go get help on a Caremark problem?
~Discouraged: 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?
~Discouraged: I'd give them a three out of five on communication.
GetHuman: And what about Caremark's ability to quickly and effectively address your problem?
~Discouraged: For that I would say two out of five.
GetHuman: And finally- any advice for other Caremark customers?
~Discouraged: Call them early in the day or late. Don't forget any personal or account information you might need for Caremark to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Discouraged taken from his Caremark customer service problem that occurred on October 26th, 2017.