CVS Caremark: CVS did not take responsibility for their commu...
A CVS Caremark customer review by GetHuman user GetHuman-379776 from November 3rd, 2017
Background on GetHuman-379776's case
GetHuman: GetHuman-379776 - can you tell our other CVS Caremark customers when your case took place?
GetHuman-379776: Sure. It was evening, on October 29th.
GetHuman: Did you reach out to CVS Caremark, and if so, how?
GetHuman: And which of these common CVS Caremark customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-379776 a list of common CVS Caremark problems)
GetHuman-379776: "Lost card" was why I was trying to call.
GetHuman-379776's review of CVS Caremark customer service
GetHuman: So how would you sum up your experience for GetHuman's CVS 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.
GetHuman-379776: CVS did not take responsibility for their communication failures with my doctor so that I could get my Rx before I was without pills. I believe they are too big and getting more controlling.
GetHuman: Let's quantify your experience contacting CVS Caremark. On a scale of 1 to 5, how easy is it go get help on a CVS Caremark problem?
GetHuman-379776: 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-379776: I'd give them a one out of five on communication.
GetHuman: And what about CVS Caremark's ability to quickly and effectively address your problem?
GetHuman-379776: For that I would say five out of five.
GetHuman: And finally- any advice for other CVS Caremark customers?
GetHuman-379776: Call them early in the day or late. Don't forget any personal or account information you might need for CVS Caremark to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-379776 taken from his CVS Caremark customer service problem that occurred on October 29th, 2017.