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

What's a FieldPulse feature you ignored at first but now can't live without?

Josh Mercer

Been using FieldPulse for about three years now, and I'm curious what features other people slept on initially that are now part of your daily workflow.

For me, it was technician notes templates. I thought they were just boilerplate fluff when we first set up the system. Pro tip: set up templates for common job types with pre-filled diagnostic checklists and customer communication language. Saves me 10-15 minutes per job, and my notes are actually consistent enough that the office doesn't call me asking what I meant by "fixed the thing."

Also didn't think I'd use photo requirements on checklists until we had a dispute over whether a disconnect was properly labeled. Now I document everything, and it's saved us twice on warranty calls.

What about you all? What'd you overlook that turned out to be essential?

Parents

  • Great thread, Josh. I'm going to add something from the operations side: automated status change notifications.

    We turned them on thinking customers would find them annoying, but our no-show complaints dropped 40% in the first month. The key was customizing the message templates — we rewrote everything to sound like a human wrote it, not a system. "Your technician Marcus is finishing up his previous appointment and will arrive between 2:15 and 2:30 PM" vs. "Status: EN ROUTE. ETA: 14:17."

    Customers actually started replying to the texts to thank us for the heads up. Unreal.

  • in reply to Gwen Albright

    Ray, we had the same problem! Thanks so much for mentioning this Gwen — I think we need to look at our message templates again. Do you have an example of one that worked well? And did you set different ones for different job types or keep it simple? Really appreciate any details!

Reply Children
No Data