Avoid like the p*ague --went to labcorp for yea...
A LabCorp customer review by GetHuman user ~tonyv from November 15th, 2017
Background on ~tonyv's case
GetHuman: ~tonyv - can you tell our other LabCorp customers when your case took place?
~tonyv: Yup. It was evening, on November 8th.
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 ~tonyv a list of common LabCorp problems)
~tonyv: "I have a billing error" was why I was trying to call.
~tonyv'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.
~tonyv: Avoid like the p*ague --went to labcorp for years for the same blood work, and medicare always paid. Last visit they billled me for $***.**. Did not help me with the claim. They just sent me bills saying they will send me to collection, even though i was sending them between **-** dollers a month. Go to your hosptial lab they will tell you up front if there ia a charge.
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?
~tonyv: 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?
~tonyv: I'd give them a four out of five on communication.
GetHuman: And what about LabCorp's ability to quickly and effectively address your problem?
~tonyv: For that I would say one out of five.
GetHuman: And finally- any advice for other LabCorp customers?
~tonyv: 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 ~tonyv taken from his LabCorp customer service problem that occurred on November 8th, 2017.