VitalChek: Horrible place to get you b*certificate had adr...
A VitalChek customer review by GetHuman user GetHuman-283415 from November 26th, 2017
Background on GetHuman-283415's case
GetHuman: GetHuman-283415 - can you tell our other VitalChek customers when your case took place?
GetHuman-283415: Yes I can. It was evening, on November 16th.
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-283415 a list of common VitalChek problems)
GetHuman-283415: "Can't Fax ID" was why I was trying to call.
GetHuman-283415'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-283415: Horrible place to get you b*certificate had adress wrong didnt take pdf documents that they said thay take fax requirements are ridiculous cancelled the order yet they still charged me never use this service
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-283415: I'd give them a three 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-283415: 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-283415: For that I would say three out of five.
GetHuman: And finally- any advice for other VitalChek customers?
GetHuman-283415: 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-283415 taken from his VitalChek customer service problem that occurred on November 16th, 2017.