Thread regarding State Farm Insurance layoffs

What is with all the Injury employees getting reassigned?

Injury only, please share what you were told. How in the world can Injury be reassigning people to areas like Express or Fire? Last time I heard everyone in Injury is still st–––––g out everyday with the work load and is still an insane asylum over there. What gives and what lame arzzsss explanation did your leadership give?

by
| 2791 views | | 11 replies (last April 23, 2021) | Reply
Post ID: @OP+1as1BxZo

11 replies (most recent on top)

Prior post correction, .....and with all due respect they know exactly what they are doing. We are all in the same boat but make no mistake about it, burnt out, high turnover means expenses and salary stay low. Keep people apart, work them so much they rarely have time to interact, and you can avoid the union push or trends to take to HR.

Most TMs when they started were usually the lowest paid employees on their team and eventually caught up. These days that is super rare. I see what newer TMs make and what older TMs make and it is a complete joke. The salary range may go up to $138K but at 1–2% merit increases every year they will never even get close to seeing that salary for new TMs. Newer and older CS's are in the exact same boat. Again all by design and usual smoke and mirrors.

by
| | Reply
Post ID: @3kzg+1as1BxZo

From 2016 to 2018 my department was on mandatory OT. One of the VPs came to visit and said that they weren't aware that we had been on OT for so long. Yeah right!! Leadership has no clue what they're doing!

by
| | Reply
Post ID: @2yyy+1as1BxZo

Probably their planmed telephony amd service model amd call toting “”system” and people’s making those changes and decisions. And lack of real “leadership”. SAP plan. Guessing that’s the driver. Perhaps.

by
| | Reply
Post ID: @2fiw+1as1BxZo

In 2016, we were “standing up” the new demand pools. We still had experienced adjusters that were handling all the older claims. The new hires were learning how to handle the new claims. It went OK at first as the new employees had no inventory to start with. When the Legacy employees got their QTDs and the older files got moved downstream, we realized that the new hires were ill prepared to handle the complex older stuff. History is about to repeat itself.

by
| | Reply
Post ID: @2nnm+1as1BxZo

What happened in 2016?

by
| | Reply
Post ID: @2jyl+1as1BxZo

Tipsord and claims VP are running the company into the ground. The cookie is literally crumbling and they are pushing it past the point of return. Upper leadership is acting like a mindless drone. Get ready for another 2016 situation where sh–t hit the fan.

by
| | Reply
Post ID: @2ovn+1as1BxZo

LOL!!! it's State Farm they think the rules/physics do not apply to them, just because they say so, and command it! They try to put 15 gallons of sh–t in a 10 gallon bucket and can't understand why everyone has it on their shoes and it stinks! The spreadsheet didn't say that is supposed to happen.

by
| | Reply
Post ID: @1ros+1as1BxZo

Ha ha ha! SF needs to learn unlike a micro chip, they can only put 10 lbs of sh–t in a 10 lb bucket. It gets pretty messy when you put 20 lbs in a 20 lb bucket and it stinks to high heaven!

by
| | Reply
Post ID: @1sda+1as1BxZo

Edit, only thought that I hope the carrier I go through doesn’t have me on hold for 30minutes. I was blown away at our sh–t service.

by
| | Reply
Post ID: @1uph+1as1BxZo

Lmao I transferred a way misrouted call to injury, got hit with a 30 minute hold time, told the customer good luck and I hope my OIC doesn’t do the same to me if that happens.

by
| | Reply
Post ID: @1njg+1as1BxZo

To my knowledge, only the slappys have been reassigned. My POD and another I have a buddy in lost 25% our team to ILR/EXP. My guess is they wanna see how far back they can cut and still keep the machine running. Go in, take your calls, keep your series current and don’t buy in to the “Work OOGs for the TEAM or take calls during Production for the TEAM” and you’ll be much happier.

by
| | Reply
Post ID: @lxq+1as1BxZo

Post a reply

: