VitalChek: They are having technical difficulties. I will...
A VitalChek customer review by GetHuman user ~bobuck from November 19th, 2017
Background on ~bobuck's case
GetHuman: ~bobuck - can you tell our other VitalChek customers when your case took place?
~bobuck: Yeah. It was morning, on November 12th.
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 ~bobuck a list of common VitalChek problems)
~bobuck: "Account Access" was why I was trying to call.
~bobuck'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.
~bobuck: They are having technical difficulties. I will have to call back later. The website would not even come up. Been waiting for over * weeks for two different birth certificates. been in contact all this time. They say I haven't sent in what is required. How many times do I need to fax the same information* What a bunch of crock.
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?
~bobuck: 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?
~bobuck: I'd give them a one out of five on communication.
GetHuman: And what about VitalChek's ability to quickly and effectively address your problem?
~bobuck: For that I would say four out of five.
GetHuman: And finally- any advice for other VitalChek customers?
~bobuck: 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 ~bobuck taken from his VitalChek customer service problem that occurred on November 12th, 2017.