VitalChek: I DID have to wait a few a minutes to speak to...
A VitalChek customer review by GetHuman user GetHuman-384059 from November 11th, 2017
Background on GetHuman-384059's case
GetHuman: GetHuman-384059 - can you tell our other VitalChek customers when your case took place?
GetHuman-384059: Yes. It was middle of the night, on November 4th.
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-384059 a list of common VitalChek problems)
GetHuman-384059: "Account Access" was why I was trying to call.
GetHuman-384059'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-384059: I DID have to wait a few a minutes to speak to someone, which is the only reason I'm giving * of * instead of *. However, once I got a representative, he was very helpful and resolved my issue immediately.
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-384059: 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?
GetHuman-384059: I'd give them a two out of five on communication.
GetHuman: And what about VitalChek's ability to quickly and effectively address your problem?
GetHuman-384059: For that I would say five out of five.
GetHuman: And finally- any advice for other VitalChek customers?
GetHuman-384059: 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-384059 taken from his VitalChek customer service problem that occurred on November 4th, 2017.