VitalChek: I was so amazed at how quickly they contacted m...
A VitalChek customer review by GetHuman user GetHuman-198340 from November 16th, 2017
Background on GetHuman-198340's case
GetHuman: GetHuman-198340 - can you tell our other VitalChek customers when your case took place?
GetHuman-198340: Yes I can. It was morning, on November 15th.
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-198340 a list of common VitalChek problems)
GetHuman-198340: "Can't Fax ID" was why I was trying to call.
GetHuman-198340'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-198340: I was so amazed at how quickly they contacted me, processed my order and how my stuff was delivered to my door in only ** hours after I ordered! If I ever need a service like this again I will turn straight to Vitalchek!
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-198340: 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-198340: I'd give them a three out of five on communication.
GetHuman: And what about VitalChek's ability to quickly and effectively address your problem?
GetHuman-198340: For that I would say two out of five.
GetHuman: And finally- any advice for other VitalChek customers?
GetHuman-198340: 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-198340 taken from his VitalChek customer service problem that occurred on November 15th, 2017.