• Replies 10 replies
  • Subscribers 2 subscribers
  • Views 12 views
  • Users 0 members are here
Options
Related

Anyone else struggling with technicians not using the mobile app consistently?

Ray DeLuca

Look, I know this isn't a new problem, but I'm hitting a wall here. We've got 14 techs in the field, and I'd say maybe 6 of them are actually updating job status in real time. The rest? They'll mark everything "complete" at 4:30 PM from their driveway. Or worse, they don't mark anything at all and I spend my mornings playing detective.

We've tried:

  • Weekly reminders in the team meeting (ignored)
  • Making it "required" in their performance eval (too vague to enforce)
  • Texting individuals when jobs sit open (works for a day)

The frustrating part is the app works fine. They all have company phones. It's not a technical problem, it's a... I don't know, behavioral thing? Cultural?

I'm not looking for lectures about accountability. I want to know what actually worked for your teams. Bonus points if you figured out how to get buy-in from guys who've been doing this job for 15+ years and think paperwork is for "the office people."

...and yes, I've seen the mobile app update post. New dashboard looks nice. Doesn't help if they don't open it.

Parents

  • Jumping in late here — the team just showed me this thread. We're a smaller operation (8 techs) and struggled with the same thing.

    What worked for us was actually slowing down the rollout. We picked 2 techs who were already pretty comfortable with phones, got them fully bought in, then had them do brief demos at our weekly huddle. Peer proof of concept > management mandate, in our experience.

    Also, we made sure every tech could force a manual sync when they needed to — took away the "it didn't save" excuse. Once they trusted the app wouldn't lose their work, compliance went way up.

    Really appreciate everyone sharing the harder-line approaches too — good to know what's in our back pocket if this soft approach stops working!

Reply

  • Jumping in late here — the team just showed me this thread. We're a smaller operation (8 techs) and struggled with the same thing.

    What worked for us was actually slowing down the rollout. We picked 2 techs who were already pretty comfortable with phones, got them fully bought in, then had them do brief demos at our weekly huddle. Peer proof of concept > management mandate, in our experience.

    Also, we made sure every tech could force a manual sync when they needed to — took away the "it didn't save" excuse. Once they trusted the app wouldn't lose their work, compliance went way up.

    Really appreciate everyone sharing the harder-line approaches too — good to know what's in our back pocket if this soft approach stops working!

Children
No Data