LabCorp: the never answered the phone. Was on hold * tim...
A LabCorp customer review by GetHuman user GetHuman-399016 from November 20th, 2017
Background on GetHuman-399016's case
GetHuman: GetHuman-399016 - can you tell our other LabCorp customers when your case took place?
GetHuman-399016: Sure. It was evening, on November 10th.
GetHuman: Did you reach out to LabCorp, and if so, how?
GetHuman: And which of these common LabCorp customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-399016 a list of common LabCorp problems)
GetHuman-399016: "I need to change my appointmen" was why I was trying to call.
GetHuman-399016's review of LabCorp customer service
GetHuman: So how would you sum up your experience for GetHuman's LabCorp 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-399016: the never answered the phone. Was on hold * times for over ten minutes each. They never answer, just the Labcorp Service Recording. Over and Over again. Promises, promises " our call is important to us". Go somewhere else and tell your health insurance.
GetHuman: Let's quantify your experience contacting LabCorp. On a scale of 1 to 5, how easy is it go get help on a LabCorp problem?
GetHuman-399016: 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-399016: I'd give them a five out of five on communication.
GetHuman: And what about LabCorp's ability to quickly and effectively address your problem?
GetHuman-399016: For that I would say two out of five.
GetHuman: And finally- any advice for other LabCorp customers?
GetHuman-399016: Call them early in the day or late. Don't forget any personal or account information you might need for LabCorp to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-399016 taken from his LabCorp customer service problem that occurred on November 10th, 2017.