--- title: "Maintenance Agreements" url: "https://fieldcamp.ai/hvac-software/maintenance-agreements/" date: "2026-07-27T09:46:19+00:00" modified: "2026-08-07T12:08:51+00:00" type: "Article" resource: "https://fieldcamp.ai/hvac-software/maintenance-agreements/" timestamp: "2026-08-07T12:08:51+00:00" author: name: "Jeel Patel" categories: - "Uncategorized" word_count: 3058 reading_time: "16 min read" summary: "Home›HVAC Software›Maintenance Agreements" description: "Manage HVAC maintenance agreements end to end — coverage tiers, auto-generated visits, renewal reminders and recurring billing, tracked against every site ..." keywords: "Uncategorized" language: "en" schema_type: "Article" related_posts: - title: "FieldCamp vs ZenMaid: Which Cleaning Business Software Wins in 2026?" url: "https://fieldcamp.ai/cleaning-business-software/fieldcamp-vs-zenmaid/" - title: "How to Price Landscaping Jobs in 2026 (with Calculator & Profit Tips)" url: "https://fieldcamp.ai/landscaping-software/how-to-price-landscaping-jobs/" - title: "10 Best HVAC Scheduling Software Platforms in 2026" url: "https://fieldcamp.ai/hvac-software/best-scheduling/" --- # Maintenance Agreements _Published: July 27, 2026_ _Author: Jeel Patel_ [Home](/)›[HVAC Software](/hvac-software/)›Maintenance Agreements HVAC · Maintenance Agreements # HVAC maintenance agreement software where the plan runs — sold, scheduled, billed and renewed on one record. A maintenance agreement only pays off if it actually happens. FieldCamp holds the plan’s frequency, covered equipment, term, and price as a record — then [a configured recurring workflow creates the visits](https://docs.fieldcamp.ai/job-management/recurring-jobs), the completed visit feeds billing, and the renewal is tracked before it lapses. It’s the agreement layer of FieldCamp’s [HVAC software](/hvac-software/). [Book a 15-minute call](https://calendly.com/jeel-fieldcamp/30min)We’ll build a plan and its recurring visits on the call. One record proposal → agreement → visits → renewal Configured recurring workflow creates the work Tracked term and renewal, before it lapses Agreements · PipelineRunning itselfDraft3Comfort Club · Nguyen Home Good-better-best · EST-2107 Awaiting e-sign2 more draftsActive214Gold plan · Chen Residence 2 visits/yr · covers 3 systems Fall tune-up auto-createdCommercial PM · Lakeside Quarterly · 4 rooftop units Renewal due9Comfort Club · Rivera Duplex Term ends Mar 1 · day 60 today Renewal email sent itselfGold plan · Harbor Dental Term ends Mar 15 Expired5Essential · 44 Birch St Lapsed Dec 14 In the win-back queue4 more expiredJust now: Rivera Duplex hit day 60 → the renewal email went out from the agreement’s terms. A reply books the spring visit. 60-day renewal email sent itself9 due · 0 chased by hand**Customer maintenance plans** — residential memberships and commercial service contracts, one engine. Memberships Commercial PM Multi-site Renewals 01 How a plan runs ## Sell → schedule → deliver → bill → renew. *Each step connected to the last.* A promise like “two tune-ups a year” becomes an operation instead of a reminder someone is supposed to act on — because every stage reads the same agreement record rather than a spreadsheet row. 1 Sell ### Sold as a proposal The plan is sold like any estimate — often as tiered membership options — a proposal the customer approves and signs, built with the same [HVAC estimating](/hvac-software/estimating/) tools. The sale and the agreement are one record. Sold 2 Schedule ### Recurring work is created A configured recurring workflow creates the required jobs or visits from the agreement’s frequency and coverage, on the same [HVAC scheduling](/hvac-software/scheduling/) board as everything else. On the calendar 3 Deliver ### The tune-up gets done A plan visit is just a job — assignable and sequenced by the [dispatcher](/hvac-software/dispatch/) like any other. The technician performs the work and the equipment record updates as the visit closes. Completed 4 Bill ### The completed visit feeds billing A closed visit carries its agreement and job context into the billing step. A person or a configured workflow raises the [invoice](/hvac-software/invoicing/) — and if the customer is on auto-pay, their saved default card is charged once that invoice exists. Invoiced 5 Renew ### The renewal is prompted The agreement’s term is tracked and its renewal surfaced before it lapses. When the customer calls, the [AI receptionist](/hvac-software/ai-receptionist/) already knows the plan they’re on. Renewed ✱ If it lapses ### It lands in a queue, not a void An expired plan moves to a win-back state rather than disappearing — so a lapsed customer is a follow-up, not a loss you notice a year later. Win-back **What’s automatic and what isn’t.** The recurring work is created by a workflow you configure. Scheduling, assignment, and the billing step remain explicit operations — FieldCamp doesn’t silently invoice a visit or auto-renew a contract on your behalf. Auto-pay charges a saved card *after* an invoice exists, not instead of one. 02 What it is ## What is HVAC maintenance *agreement software?* HVAC maintenance agreement software stores the agreement record, covered equipment, frequency, renewal date, and price. Configured recurring workflows create the required jobs or visits. In practice it manages the seasonal tune-up memberships and service contracts customers sign up for — from selling the plan to scheduling its visits, billing them, and renewing the agreement. It turns a promise into connected records with explicit ownership: a configured workflow creates recurring work, a person or verified workflow handles billing, and the agreement tracks covered equipment. **Why it matters** : a maintenance base is recurring revenue and retention in one — the most stable revenue an HVAC business has, and the strongest reason a customer stays yours instead of the next contractor’s. But the failure mode is administrative: plans sold and then forgotten, tune-ups that don’t get booked, renewals that lapse, visits done but never billed. Software that connects the plan’s lifecycle is the difference between a program that compounds and one that quietly leaks. → **Service agreements, not facility maintenance**. This is about plans your *customers* buy. Managing your own building’s equipment upkeep is a different category — a CMMS — and “HVAC maintenance software” gets sold under both meanings. Check which one a vendor means before you compare anything. Memberships · TiersTrackedESEssential · 1 visit/yr Fall furnace tune-up · reminder texts 112 customersCOComfort · 2 visits/yr Spring AC + fall furnace · priority booking 78 customersGDGold · 2 visits + repair discount All systems covered · billed per visit 24 customersLPLapsed > 90 days Win-back queue · renewal drafted PromptedTiers are select options you define＋ Add tier 3 tiers · 214 customers — entitlements on the record ### Who it’s for Residential HVAC · tune-up memberships Seasonal tune-up memberships — spring AC, fall furnace — sold as tiered options and run as recurring revenue, with reminders before each visit. Commercial HVAC · service contracts Service contracts with scheduled [preventive-maintenance visits](/hvac-software/commercial/preventive-maintenance/) across sites — rooftop units and covered equipment tracked per location, visits and billing per the contract’s terms. ★ Any shop with a maintenance base · off the spreadsheet Move agreement terms, recurring-work configuration, billing context, and renewal follow-up from a spreadsheet into connected records. 03 Core capabilities ## What service agreement software must do — *each one handled natively.* These are the capabilities that decide whether a maintenance program compounds or quietly leaks — the checklist to evaluate any tool against. ### Sell the plan as a proposal A maintenance agreement is sold like any estimate — a proposal the customer approves and signs — so the sale and the plan are one record from day one. No re-keying the agreement into a second system after the customer says yes. ### Memberships & tiers Plans and membership levels tracked per customer, with the entitlements each includes — visits per year, priority booking, repair discounts. Tiers are a record, not a spreadsheet column. ### Configured recurring jobs or visits A configured recurring workflow creates the required jobs or visits using the agreement’s frequency and coverage. Scheduling and dispatch remain explicit downstream steps. ### Equipment under the plan The units a plan covers are tracked on the customer’s equipment record, with a lifecycle stage — so service history and warranty stay attached to the unit. It’s the same record your [HVAC CRM](/hvac-software/crm/) works from when the customer calls. ### Billing on completion When a maintenance visit closes, its agreement and job context carry into the billing step, raised by a person or a configured workflow. Combined with auto-pay on a saved card, the recurring base can collect without a phone call. ### Renewals and win-back The agreement’s term is tracked and its renewal prompted before it lapses, so plans don’t silently expire. Lapsed plans land in a win-back state instead of disappearing. ### Agreement pipeline Draft, active, renewal-due, and expired are stages on a pipeline you can name and colour yourself — so the health of the maintenance base is a board, not a report someone builds. ### Custom fields on the agreement Add your own properties — a contract number, a coverage exclusion, a purchase-order reference — because the agreement is a configurable object rather than a fixed form. 04 The FieldCamp difference ## Connect the agreement lifecycle *on one data model.* In most shops a maintenance agreement is a line in a spreadsheet and a reminder someone is supposed to act on. In FieldCamp it’s a record the whole operation reads — the proposal, the plan, its visits, its invoices, and its renewal are stages of one thing. Which is why a plan visit is dispatchable like any job, why the covered unit’s history is already on the record when a technician arrives, and why the CSR taking the call can see the tier the customer is on. No two maintenance programs are alike — a team can start with the template, and a multi-crew commercial operation can add its own stages, agreement fields, and approval workflow on the same system. 01 Proposal tiered options, signed 02 Agreement tier, term & billing terms 03 Visits configured recurring work 04 Renewal tracked & prompted 05 Configurable agreements ## Residential memberships. Commercial contracts. *Same engine.* A tune-up membership and [a multi-site preventive-maintenance contract](https://docs.fieldcamp.ai/data-model/commercial-hvac) are the same object with different terms — visits, billing, covered equipment, renewal. FieldCamp runs both, because the [data model is customizable](/customizable-data-model/) rather than a fixed template. Residential membershiptiers, entitlements, seasonal tune-upsCommercial contractmulti-site PM visits, per-location equipmentSame engineone agreement object, different termsStart on the out-of-box HVAC layout, then reshape objects, fields, statuses, and workflows to how your maintenance program actually runs. There is no “you’ve outgrown it” migration cliff between the two. What both share - **Visits** — a configured recurring workflow creates the required jobs from the plan’s frequency, whether that is two tune-ups a year or twelve rooftop calls.- **Billing** — the completed visit carries agreement context into the billing step, and auto-pay can charge a saved card once the invoice exists.- **Covered equipment** — the units a plan applies to sit on the customer’s equipment record with a lifecycle stage, per site for a commercial contract.- **Renewal** — the term is tracked and prompted before it lapses, and an expired plan moves into win-back instead of vanishing. The straight talk - The recurring work is created by a workflow you configure. Scheduling, assignment, and the billing step stay explicit operations — nothing is invoiced or renewed silently.- Auto-pay charges a saved card *after* an invoice exists, not instead of one — the invoice is still a record you can see and correct.- These are customer service agreements, not a CMMS for your own facility — the same phrase is sold under both meanings, so confirm which one a vendor means. 06 Integrations ## Recurring revenue that *reaches your books.* A maintenance program shouldn’t live in a silo. The invoices a plan raises and the visits it schedules connect to accounting and calendars through separately configured integrations — including the [QuickBooks Online connection](/hvac-software/quickbooks/) for supported customer, estimate, and invoice records. QuickBooks Online. FieldCamp supports configured workflows for customers, estimates, and invoices. QuickBooks Desktop is not claimed here. Plan invoices carry their context. A completed visit reaches billing with its agreement and job attached, so the invoice that lands in accounting already says what it was for. Each integration is configured separately. Accounting and calendar connections are set up per your requirements. Confirm the exact mapping during onboarding before relying on it in a production accounting workflow. ConnectedSyncedQBQuickBooks Plan invoices & payments Synced ✓XWXero / Wave Accounting sync Synced ✓GCGoogle / Outlook Calendar Plan visits & availability Synced ✓TWTwilio SMS Visit reminders & confirmations Live ✓ Plan invoice posted · zero re-keying07 Compare ## How to compare *agreement software.* Use the same criteria on every product you evaluate — including ours. Verify each competing claim against that vendor’s own current documentation rather than a comparison page. | Criterion | FieldCamp | What to ask the other vendor | |---|---|---| | Selling the agreement | Sold as a proposal the customer signs — the sale and the plan are one record | Is the plan set up in the back office after the sale, or created by it? | | Creating plan visits | Configured recurring workflows create jobs or visits from the agreement | Is it a real recurrence engine, or duplicated jobs someone copies forward? | | Billing delivered visits | Completed visit carries agreement context into a billing step; auto-pay can charge a saved card | What is automatic, what is configurable, and what still needs a person? | | Renewals | Term tracked, renewal prompted before it lapses; expired plans enter a win-back state | What happens the day a term runs out — a prompt, or silence? | | Equipment under the plan | Covered units on the customer’s equipment record with lifecycle stages | Is coverage a PDF, a field, or a real link to the unit? | | Extensibility | Your own agreement fields, pipeline stages, and approval workflow | Can you add a contract number or exclusion without a developer? | | Data model | Plan, visits, invoices, equipment and renewals on one model | One record, or a module that syncs to the others? | | Category | Customer service agreements | Is the product actually a CMMS for your own facility? | The frame that matters: an agreement is only worth selling if its visits actually get created, delivered, billed and renewed. Ask every vendor to walk one plan through that whole loop on a live record rather than a slide. 08 How to choose ## How to choose maintenance agreement software — *six questions.* Whichever tool you evaluate — including ours — put these to it. If the demo can’t show an answer, a person will still be chasing the plan. 01 ### How are recurring plan visits created? Configured recurring workflows create required jobs or visits from agreement context. Scheduling and assignment remain explicit operational steps. 02 ### How does billing work after a visit? Agreement and completed-work context should carry into invoice creation. Ask who owns that step, and whether a saved card can be charged once the invoice exists. 03 ### Does it track renewals? Lapsed plans are lost revenue. The term should be tracked and the renewal prompted before it runs out — and an expired plan should go somewhere, not nowhere. 04 ### Does it tie to the equipment record? Coverage, service history, and warranty should stay attached to the unit — not to a PDF in a folder. 05 ### Can you sell the plan in the same system? Proposal → agreement → operation on one record. If the sale lives in another tool, the plan starts life re-keyed. 06 ### Service agreements or CMMS? Confirm you’re buying customer maintenance plans, not facility asset upkeep — the same phrase is sold under both meanings. 09 Why it pays ## The maintenance base is the business. *Run it like one.* Maintenance agreements are recurring revenue and retention in one — and the value only shows up when the plans actually run. 01 ### Predictable recurring revenue The most stable revenue in the business — booked in advance, delivered on schedule, billed on completion. 02 ### Higher retention Plan customers renew and refer. The agreement is the reason they call you — not whoever’s ad they saw in July. 03 ### Less admin leakage Fewer plans sold, delivered, then un-billed or un-renewed. When each stage reads the same record, the gaps get visible instead of quiet. 04 ### Full equipment history Every plan visit lands on the covered unit’s record — so diagnoses are faster and replacement conversations are grounded in history. 05 ### A sellable asset A healthy maintenance base raises the value of the business itself — recurring contracts are what an acquirer actually pays for. 10 Glossary ## The agreement terms that matter. Maintenance agreement / service contract A recurring plan a customer buys for scheduled tune-ups and preventive maintenance. Membership A tiered version of a maintenance plan with defined entitlements — visits per year, priority booking, discounts. Covered equipment The specific units a plan applies to, held on the customer’s equipment record. Recurring workflow The configured automation that creates a plan’s jobs or visits on its cadence. Renewal Extending the agreement before its term lapses — tracked and prompted, so plans don’t silently expire. Win-back The state a lapsed plan moves into so it can be followed up rather than lost. Auto-pay Charging a saved default card automatically once a recurring invoice has been generated. CMMS Computerised maintenance management for a facility’s own equipment — a different category from customer service agreements. 11 FAQ ## Maintenance agreements, *answered.* **What is HVAC maintenance agreement software?** Software that stores the agreement record, its covered equipment, frequency, renewal date, and price — and creates the required jobs or visits through configured recurring workflows. It covers selling the plan, scheduling its visits, billing them, and renewing the agreement. **How do plan visits get created?** A configured recurring workflow creates the required jobs or visits from the agreement’s frequency and coverage. Scheduling and assignment remain explicit operational steps on the same board as the rest of your work. **Does it invoice the visit automatically?** A completed visit carries its agreement and job context into the billing step, and a person or a configured workflow raises the invoice. If the customer is on auto-pay, their saved default card is charged once that invoice exists — but FieldCamp does not silently invoice a visit on your behalf. **Does it track renewals?** Yes. The agreement’s term is tracked and its renewal prompted before it lapses. An expired plan moves into a win-back state rather than disappearing from view. **Can I sell the plan in the same system?** Yes — the agreement is sold like any estimate, as a proposal the customer approves and signs. The sale and the plan are one record, so nothing is re-keyed after the customer says yes. **Does it handle membership tiers?** Yes. Plans and membership levels are tracked per customer with the entitlements each includes — visits per year, priority booking, repair discounts. **How is covered equipment tracked?** The units a plan covers sit on the customer’s equipment record with a lifecycle stage, so service history and warranty stay attached to the unit rather than to the agreement document. **Does it work for commercial contracts, not just residential memberships?** Yes — they’re the same object with different terms. Commercial contracts carry scheduled preventive-maintenance visits across sites, with covered equipment tracked per location. **Can I add my own fields and stages?** Yes. The agreement is a configurable object — add a contract number, a coverage exclusion, or a purchase-order reference, and name your own pipeline stages. **Is this the same as a CMMS?** No. A CMMS manages a facility’s own equipment upkeep. This manages the maintenance plans your customers buy. The phrase “HVAC maintenance software” is used for both, so confirm which one a vendor means. **How much does it cost?** Pricing depends on operating requirements and implementation scope. A demo should verify the agreement record, recurring-work configuration, the billing step, renewal tracking, and accounting mappings. 12 Related ## The rest of the HVAC platform. [HVAC Software The whole platform this agreement belongs to — data model, scheduling, dispatch, CRM, billing.](/hvac-software/)[HVAC Scheduling Where the plan’s recurring visits land on the calendar.](/hvac-software/scheduling/)[HVAC Dispatch A plan visit is a job — assigned and sequenced like any other.](/hvac-software/dispatch/)[HVAC Invoicing Where a completed plan visit becomes a bill, with auto-pay on saved cards.](/hvac-software/invoicing/)[HVAC Estimating The proposal tool the plan is sold with — often folded into the better and best tiers.](/hvac-software/estimating/)[HVAC CRM The customer record holding the tier, the covered units, and the history.](/hvac-software/crm/)[Preventive Maintenance Commercial PM routes scheduled against contracts and covered equipment.](/hvac-software/commercial/preventive-maintenance/)[Commercial Asset Management The equipment records a plan renews against, per site.](/hvac-software/commercial/asset-management/)[AI Receptionist Knows the plan a caller is on before the conversation starts.](/hvac-software/ai-receptionist/) Get started ## See agreements and recurring work *stay connected.* Fifteen minutes. We’ll sell a plan as a proposal, configure its recurring visits, close one, and follow it into billing and renewal — on your operating requirements. [Book a 15-minute call](https://calendly.com/jeel-fieldcamp/30min) --- _View the original post at: [https://fieldcamp.ai/hvac-software/maintenance-agreements/](https://fieldcamp.ai/hvac-software/maintenance-agreements/)_ _Served as markdown by [Third Audience](https://github.com/third-audience) v3.6.1_ _Generated: 2026-08-07 12:08:52 UTC_