CVS Caremark: paper claim status
Una recensione del cliente CVS Caremark da parte dell'utente GetHuman GetHuman-caselaw da dicembre 8º, 2017
Background on GetHuman-caselaw's case
GetHuman: GetHuman-caselaw - can you tell our other CVS Caremark customers when your case took place?
GetHuman-caselaw: Yeah. It was afternoon, on novembre 30º.
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-caselaw a list of common CVS Caremark problems)
GetHuman-caselaw: "Lost card" was why I was trying to call.
GetHuman-caselaw'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-caselaw: paper claim status
GetHuman: Can you tell the rest of us a bit more from what happened on 11/30/17?
GetHuman-caselaw: sent in paper claim -- have not heard anything in over ** days
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-caselaw: 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-caselaw: I'd give them a two out of five on communication.
GetHuman: And what about CVS Caremark's ability to quickly and effectively address your problem?
GetHuman-caselaw: For that I would say three out of five.
GetHuman: And finally- any advice for other CVS Caremark customers?
GetHuman-caselaw: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per CVS Caremark sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-caselaw taken from his CVS Caremark customer service problem that occurred on novembre 30º, 2017.