LabCorp: Called once and was hung up on when I didn't ha...
A LabCorp customer review by GetHuman user GetHuman-53010 from November 28th, 2017
Background on GetHuman-53010's case
GetHuman: GetHuman-53010 - can you tell our other LabCorp customers when your case took place?
GetHuman-53010: Yes I can. It was morning, on November 20th.
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-53010 a list of common LabCorp problems)
GetHuman-53010: "I need to change my appointmen" was why I was trying to call.
GetHuman-53010'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-53010: Called once and was hung up on when I didn't have an invoice number. (I was calling to find out why I hadn't been invoiced!) Called again and was eventually able to get it taken care of. Very, very long wait on hold with a highly irritating music loop.
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-53010: 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-53010: I'd give them a three out of five on communication.
GetHuman: And what about LabCorp's ability to quickly and effectively address your problem?
GetHuman-53010: For that I would say four out of five.
GetHuman: And finally- any advice for other LabCorp customers?
GetHuman-53010: 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-53010 taken from his LabCorp customer service problem that occurred on November 20th, 2017.