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
  • We've been testing a hybrid: customer custom fields for contract metadata, plus a specific work order template for contract visits that auto-tags and auto-fills the billing reference. The template pulls the contract # from the customer field into the WO description.

    Still manual for renewals but it's cut our setup time per visit significantly. Happy to share the template export if anyone's interested.

Reply
  • We've been testing a hybrid: customer custom fields for contract metadata, plus a specific work order template for contract visits that auto-tags and auto-fills the billing reference. The template pulls the contract # from the customer field into the WO description.

    Still manual for renewals but it's cut our setup time per visit significantly. Happy to share the template export if anyone's interested.

Children
No Data