3 ms·

That may be true but seems like Zenefits did not really focus on product building. Otherwise these kind of incidences should not be happening (customer details

by achow 11y ago

That may be true but seems like Zenefits did not really focus on product building. Otherwise these kind of incidences should not be happening (customer details getting ‘lost’).. Arroyo, who runs the Los Angeles software agency, made Zenefits his company’s health insurance broker in 2014. He experienced a string of minor problems at first, he said — annoyances like an inability by Zenefits reps to explain a mysterious charge on his insurance bill. Then, last fall, he was told he would have to submit to a random audit by his insurance carrier. He gave his information to Zenefits, trusting that it would make its way to the carrier. “A week or two later, I got a letter saying I wasn’t compliant, and our insurance had been canceled,” he said. Zenefits, he said, “never gave me an answer of what happened. They just said, ‘Oh, it must have gotten lost somewhere.’” Arroyo dropped Zenefits in December.

dkarapetyan 11y ago
The adversarial nature of integrating with payroll, insurance, and healthcare providers does not help when it comes to building such systems. Everyone is mistrustful and there are no APIs or SLAs to speak of. So I agree that Zenefits can and should do more to smooth out the wrinkles in the system as much as possible and dropping the ball is not cool. Even large company payroll and insurance systems go awry more frequently than you'd think would be acceptable. My paycheck at pretty large companies has been adjusted more than a few times because of "clerical" errors in ADP or the in-house integration component. There have also been a few times where my insurance paperwork has been lost in the sea of other paperwork and I've had to reach out to HR to get things fixed. Go around and ask people how much they like ADP and Trinet. Chances are you'll find more than a few customers that hate them with a passion. Not just because of clerical errors like the ones I mentioned but because of how bloated and error prone their products are. I recently had to change my address in the ADP online portal and I couldn't do it. I had to reach out to both their customer support and my previous employer to get them to change a single text field.

by achow 11y ago

dkarapetyan 11y ago

The adversarial nature of integrating with payroll, insurance, and healthcare providers does not help when it comes to building such systems. Everyone is mistrustful and there are no APIs or SLAs to speak of. So I agree that Zenefits can and should do more to smooth out the wrinkles in the system as much as possible and dropping the ball is not cool. Even large company payroll and insurance systems go awry more frequently than you'd think would be acceptable. My paycheck at pretty large companies has been adjusted more than a few times because of "clerical" errors in ADP or the in-house integration component. There have also been a few times where my insurance paperwork has been lost in the sea of other paperwork and I've had to reach out to HR to get things fixed. Go around and ask people how much they like ADP and Trinet. Chances are you'll find more than a few customers that hate them with a passion. Not just because of clerical errors like the ones I mentioned but because of how bloated and error prone their products are. I recently had to change my address in the ADP online portal and I couldn't do it. I had to reach out to both their customer support and my previous employer to get them to change a single text field.