How do you structure your service agreements in FieldPulse?

We've got about 40 commercial HVAC clients on annual maintenance agreements and I'm trying to figure out the cleanest way to handle this in FieldPulse without creating a mess.

Right now we're creating recurring work orders for each quarterly visit, but that means 4 separate WOs per customer per year and no real visibility into "this customer is under contract" vs "this is a one-off."

Also billing is a pain. Some customers prepay the year, some pay quarterly, some we invoice after each visit. FieldPulse doesn't seem to have a "service agreement" object so I'm hacking it with tags and custom fields.

What's actually working for people? Am I missing something obvious or is this just not what the tool was built for?

Parents
  • Hi Mike! Thanks for bringing this up — service agreements are definitely a hot topic with our larger customers.

    I wanted to share that we're actively exploring a more native service agreement feature for 2026. No timeline to commit to yet, but I'd love to connect you with our product team for a brief call if you're open to sharing more about your specific workflows. Your input would be invaluable.

    In the meantime, I'd echo Gwen and Nadia's approaches. We've seen both work well depending on team size and reporting needs.

    Feel free to DM me if you'd like to chat further!

Reply
  • Hi Mike! Thanks for bringing this up — service agreements are definitely a hot topic with our larger customers.

    I wanted to share that we're actively exploring a more native service agreement feature for 2026. No timeline to commit to yet, but I'd love to connect you with our product team for a brief call if you're open to sharing more about your specific workflows. Your input would be invaluable.

    In the meantime, I'd echo Gwen and Nadia's approaches. We've seen both work well depending on team size and reporting needs.

    Feel free to DM me if you'd like to chat further!

Children
No Data