VitalChek: I man with whom I spoke was very pleasant. He e...
A VitalChek customer review by GetHuman user ~mizzusparker from November 13th, 2017
Background on ~mizzusparker's case
GetHuman: ~mizzusparker - can you tell our other VitalChek customers when your case took place?
~mizzusparker: Yup. It was afternoon, on November 9th.
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 ~mizzusparker a list of common VitalChek problems)
~mizzusparker: "Dispute a Charge" was why I was trying to call.
~mizzusparker'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.
~mizzusparker: I man with whom I spoke was very pleasant. He explained they had had a power failure, were just coming back online and asked me to call again in ** - ** minutes. He also gave me an alternative number for a shorter wait time. Sorry, I'm not sharing that.
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?
~mizzusparker: 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?
~mizzusparker: I'd give them a four out of five on communication.
GetHuman: And what about VitalChek's ability to quickly and effectively address your problem?
~mizzusparker: For that I would say three out of five.
GetHuman: And finally- any advice for other VitalChek customers?
~mizzusparker: 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 ~mizzusparker taken from his VitalChek customer service problem that occurred on November 9th, 2017.