ADP Payroll and Benefits: never received an agent, **** poor service*have...
A ADP Payroll and Benefits customer review by GetHuman user ~lrojas from November 25th, 2017
Background on ~lrojas's case
GetHuman: ~lrojas - can you tell our other ADP Payroll and Benefits customers when your case took place?
~lrojas: Sure. It was evening, on November 17th.
GetHuman: Did you reach out to ADP Payroll and Benefits, and if so, how?
GetHuman: And which of these common ADP Payroll and Benefits customer issues best describes the reason you wanted to talk to them?
(Shows ~lrojas a list of common ADP Payroll and Benefits problems)
~lrojas: "Update Account Info" was why I was trying to call.
~lrojas's review of ADP Payroll and Benefits customer service
GetHuman: So how would you sum up your experience for GetHuman's ADP Payroll and Benefits 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.
~lrojas: never received an agent, **** poor service*have tried calling on several occasions same response, nothing.
GetHuman: Let's quantify your experience contacting ADP Payroll and Benefits. On a scale of 1 to 5, how easy is it go get help on a ADP Payroll and Benefits problem?
~lrojas: 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?
~lrojas: I'd give them a five out of five on communication.
GetHuman: And what about ADP Payroll and Benefits's ability to quickly and effectively address your problem?
~lrojas: For that I would say two out of five.
GetHuman: And finally- any advice for other ADP Payroll and Benefits customers?
~lrojas: Call them early in the day or late. Don't forget any personal or account information you might need for ADP Payroll and Benefits to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~lrojas taken from his ADP Payroll and Benefits customer service problem that occurred on November 17th, 2017.