VitalChek: They promised solutions they could not deliver...
A VitalChek customer review by GetHuman user GetHuman-320118 from November 26th, 2017
Background on GetHuman-320118's case
GetHuman: GetHuman-320118 - can you tell our other VitalChek customers when your case took place?
GetHuman-320118: Yup. It was afternoon, on November 20th.
GetHuman: Did you reach out to VitalChek, and if so, how?
GetHuman: And which of these common VitalChek customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-320118 a list of common VitalChek problems)
GetHuman-320118: "Dispute a Charge" was why I was trying to call.
GetHuman-320118's review of VitalChek customer service
GetHuman: So how would you sum up your experience for GetHuman's VitalChek 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-320118: They promised solutions they could not deliver, no promised followup contact, impossible to reach by phone, Scammed me out of $** and delayed a very important transaction. Nothing was refunded. This company should get the boot.
GetHuman: Let's quantify your experience contacting VitalChek. On a scale of 1 to 5, how easy is it go get help on a VitalChek problem?
GetHuman-320118: 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-320118: I'd give them a five out of five on communication.
GetHuman: And what about VitalChek's ability to quickly and effectively address your problem?
GetHuman-320118: For that I would say four out of five.
GetHuman: And finally- any advice for other VitalChek customers?
GetHuman-320118: Call them early in the day or late. Don't forget any personal or account information you might need for VitalChek to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-320118 taken from his VitalChek customer service problem that occurred on November 20th, 2017.