CVS: The web site was simple to use as I clicked on...
A CVS customer review by GetHuman user ~unknowcard 4873813574947 from November 2nd, 2017
Background on ~unknowcard 4873813574947's case
GetHuman: ~unknowcard 4873813574947 - can you tell our other CVS customers when your case took place?
~unknowcard 4873813574947: Sure. It was morning, on October 29th.
GetHuman: Did you reach out to CVS, and if so, how?
GetHuman: And which of these common CVS customer issues best describes the reason you wanted to talk to them?
(Shows ~unknowcard 4873813574947 a list of common CVS problems)
~unknowcard 4873813574947: "Cancel order" was why I was trying to call.
~unknowcard 4873813574947's review of CVS customer service
GetHuman: So how would you sum up your experience for GetHuman's CVS 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.
~unknowcard 4873813574947: The web site was simple to use as I clicked on praise, clicked on submit comment, entered my statement and submited it. No shutteling from page to page. Simple, clear and perfect.
GetHuman: Let's quantify your experience contacting CVS. On a scale of 1 to 5, how easy is it go get help on a CVS problem?
~unknowcard 4873813574947: 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?
~unknowcard 4873813574947: I'd give them a five out of five on communication.
GetHuman: And what about CVS's ability to quickly and effectively address your problem?
~unknowcard 4873813574947: For that I would say three out of five.
GetHuman: And finally- any advice for other CVS customers?
~unknowcard 4873813574947: Call them early in the day or late. Don't forget any personal or account information you might need for CVS to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~unknowcard 4873813574947 taken from his CVS customer service problem that occurred on October 29th, 2017.