HVAC CRM software: test customer and equipment records
Published by Relay, a field service software provider. Based on vendor documentation checked November 4, 2026, with original evaluation scenarios rather than hands-on testing.
HVAC CRM software keeps customer relationships connected to the properties, equipment, conversations, and work behind them. The buying question is whether the next person can find the right record and act on it safely, without calling you to reconstruct the last visit.
For a small contractor, test that record before comparing long feature lists. A customer with two properties, similar equipment, and a separate access contact exposes more than a tidy demonstration with one name and one address.
Compare how each product separates the records
Jobber documents multiple properties under a client. Quotes and jobs use the property; invoices use the client's billing address and also show the job property when created from a job. That gives you specific records to inspect rather than assuming every address field means the same thing.
Housecall Pro distinguishes multiple addresses from sub-customers. Its parent/child billing help sends appointment notifications to the sub-customer and invoices, estimates, and receipts to the billing parent. Ask which structure matches your communication needs before importing records.
FieldPulse describes customer sites and site contacts, including contact selection for jobs and invoices. Its asset documentation describes model, installation, warranty, lifecycle, and linked service records. Confirm the package and actual staff permissions with the seller.
These are documented capabilities, not results from comparative product trials. A missing detail in a help page does not establish that the product cannot do it.
Run one customer-record exercise before buying
Fictional demonstration: Morgan owns two properties served by your single-depot HVAC business. Alex is the access contact at Cedar. Morgan's billing address is different from either service address. Use invented names, addresses, serials, and contact details in an account the seller has made safe for demonstrations, with outbound messages and charges disabled.
| Record | What to enter |
|---|---|
| Customer and people | Morgan owns both properties. Alex provides access at Cedar. Morgan confirms who may approve extra work and receive billing documents. |
| Cedar property | An invented Cedar address, its own access instructions, and unit Cedar-41. A past job explicitly links to Cedar-41. |
| Lake property | A different invented address and unit Lake-82. Its model matches Cedar-41, but its serial number and service record differ. |
| Historical uncertainty | An older note says only ‘system checked’. It does not identify a unit. Keep that uncertainty visible instead of assigning it to whichever unit is open. |
- Open the right history. Start with Morgan's customer record, select Cedar, then open Cedar-41. Find the explicitly linked past job. Switch to Lake-82: Cedar's repair must not become Lake's repair merely because the model matches. Check that the unidentified historical note remains qualified.
- Prepare a visit without changing who pays. Create a Cedar demonstration job. Give the technician Cedar's access instructions and Alex's contact details. Preview the estimate or invoice separately: check the service address, billing identity, actual recipients, and which notes are visible. An access contact should not become the payer just because their phone is easiest to reach.
- Change a future instruction. Replace Alex with a new confirmed access contact at Cedar. Reopen Cedar's next visit and Lake's record. Identify what updated, what remains copied on an existing job, and what needs a deliberate edit. Confirm that old customer-facing documents still represent their original transaction rather than silently adopting new billing facts.
- Replace equipment without erasing service history. Retire Cedar-41 and create a distinct replacement record with a new serial. Find the old repair again, then inspect the replacement's history. The old repair should remain attributable to the old unit. Do not relabel the old unit just to make the active list look current.
The exercise tests the configured product and your team's procedure together. A vendor may require a specific record structure or an authorized manual step. Have them show it; a promise that “it's all in the notes” is not the same as demonstrating where the next technician will find it.
Leave the demonstration with four pieces of evidence
Keep a screenshot of Cedar-41's linked old repair, the technician's Cedar visit, a customer-facing billing preview, and the retired-unit history beside the new unit. Use demonstration data only. Record any extra package, permission, duplicate entry, or manual step required to produce them.
Those four artifacts let you compare the same task across vendors. If your main concern is working without signal, use the separate HVAC mobile software exercise. If it is accepting and pricing replacement work, use the HVAC estimating guide. CRM record quality supports those workflows but does not establish their completion.
Where Relay fits
Relay keeps customer properties, site contacts, equipment, notes, and linked jobs together. Equipment service history comes from jobs explicitly linked to that unit; archiving equipment preserves its historical links. Customer billing relationships and a property's optional Bill To are separate from the site contact.
For an owner working in the field, those records support the wider job: Relay's voice and SMS agents can handle customer requests and book against technician availability, travel, and protected commitments. Record quality alone does not prove a booking was confirmed or give someone authority to approve extra work. Ask us to demonstrate your contact, property, and billing arrangement as well as the booking.