HVAC mobile software: compare offline field work
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 mobile software should help a technician find the right equipment, record work at the property, and leave a usable record for whoever goes next. A phone-sized schedule alone does not establish that the job can be finished in a basement with no signal.
This guide compares business apps for service work. Refrigerant calculators, diagnostic tools, and thermostat controls serve different purposes. Use the documented offline differences below and one fictional return-visit exercise to evaluate the exact app, account, and technician permissions you would buy.
Separate viewing, recording and sending
Three questions belong in every mobile demonstration: what information is already on the phone, what work can be saved there, and what needs a connection before it takes effect? Reading a downloaded job is different from adding a photo. Saving a payment attempt is different from having a successful payment.
Have the seller name the mobile app and version, phone operating system, required plan, and user role. Repeat the demonstration with an ordinary technician account. An owner's unrestricted account can conceal permissions that will stop someone in the field.
Also distinguish no connection from a weak connection. A spinning request in a low-signal property may behave differently from a phone deliberately switched offline. Ask to see both conditions using the vendor's supported test procedure.
Compare the documented offline boundaries
Housecall Pro's Offline Mode is view-only. It automatically downloads assigned jobs for today and the next two days, up to the earliest ten per day. Opening other jobs while connected can prepare them separately. Customer history needs a connection, as do edits, job completion, and payment collection. Check the last successful sync before leaving coverage.
Jobber's connectivity guidance describes offline timers, job forms, notes, and attachments that sync after reconnection. Information from teammates can be stale; location-based timers and reports require internet. That supports a different field-capture comparison from view-only access, without establishing that every Jobber action works offline.
ServiceTitan's Field Mobile App documentation describes local status changes, notes, photos, signatures, and other supported work. Open the job online beforehand to cache its equipment history. Invoice editing is partial, and dynamic pricing needs a connection. Some payments can be captured for processing after reconnecting; card swipe and Tap to Pay require connectivity. A deferred payment is not a finalized payment.
These are summaries of vendor documentation checked November 4, 2026, rather than results of our own app trials. The ServiceTitan source concerns its Field Mobile App specifically. Confirm the deployed app, supported devices, configuration, and account permissions with each seller; do not transfer one product's offline claim to another app or version.
Run one two-unit job through loss of signal
Fictional buying exercise: a customer has upstairs and downstairs equipment at the same property. The upstairs unit needs a return visit with a part. The person paying has a different billing address. Use a demonstration account and invented records, with the seller helping keep customer messages and charges disabled.
- Prepare while connected. Assign the visit to the technician. Load the supported job data, equipment, access instructions, and required form. Open an existing attachment to check its actual contents; a filename or thumbnail does not prove the full file is available offline.
- Lose the connection. Find the service address and upstairs unit again. Follow only the vendor's supported offline workflow to record a note, photo, and required answer. If an action is unavailable, record that limitation rather than forcing it or substituting a private phone note.
- Reopen the work. Use the vendor's supported close-and-reopen procedure. Check whether the saved answer and original photo remain. Do not sign out, clear app storage, or reinstall while unsent work remains.
- Change one harmless fact from another account. While the technician is offline, have the owner add a sample access note. The phone cannot know that change yet. Inspect what happens when the phone reconnects, including any action that needs review.
- Finish the handoff while connected. Have another authorized person open the job and full photo. Find the remaining work and needed part, then prepare the return visit through the product's supported process. Ask what would happen if the first technician were unavailable tomorrow.
This exercise is a proposed buying test, not a claim that every vendor passes it. Let each seller demonstrate its process and explain any manual steps. Keep repair pricing, approvals, customer communications, and actual scheduling separate until their required checks can run.
Check what the next person actually receives
Use two observations for each piece of work: what survived on the first phone, and what another authorized person received after reconnection. This avoids calling a local save a completed business handoff.
| On the first phone | After reconnecting |
|---|---|
| Correct unit. Note and photo identify the upstairs unit | Next technician opens that unit's work, not the downstairs unit |
| Work recorded. Required answer, note and photo remain after reopening | Another authorized person can read the answer and open the photo |
| Return visit. Remaining work and needed part are recorded | Owner can tell what remains without a private text from the first technician |
| Changed information. Phone shows the version it has downloaded | After reconnecting, the owner change is visible or a conflict asks for review |
If the photo remains unsent or a change needs a decision, ask who can see that problem and how they finish it. Then repeat with a second technician after ordinary training. Record the missing information and manual steps; a numerical score with arbitrary weights is less useful than knowing which daily task your team cannot complete.
Apply the same test to Relay
Relay's iOS and Android field app brings job information, equipment, checklists, photos, estimates, and invoices onto the phone. Supported notes, photos, checklist work, and draft estimate or invoice changes can be queued for sync. The available work depends on the user's role and what the phone has downloaded; it is not a promise of every historical record or action offline.
Sending an estimate or invoice and taking an electronic payment require a connection. Queued work still has to reach Relay and pass its checks; work needing a decision surfaces for attention. Ask to demonstrate these boundaries in the app version your team will use, including opening the full photo from another authorized account.
If the main bottleneck is work arriving while the owner is on a job, also evaluate Relay's voice and SMS booking workflow. Our SMS booking guide explains how a request becomes a checked appointment. Mobile field capture and customer booking answer different parts of the day.
For customer records shared across properties, use the HVAC CRM record exercise to compare equipment history, private notes, and billing recipients while connected.
Choose around the work your team must finish
If technicians only need to read prepared job details offline, view-only access may be enough. If they must record findings and photos without coverage, make local capture and the reconnection handoff a purchase requirement. If taking payment on site matters, compare the exact payment method and connectivity requirement separately.
Keep a short written result with the app version, device, role, required package, supported tasks, and steps someone must finish later. For quote scope and customer choices, use the HVAC estimating buying guide. Choose the operating workflow your team can complete consistently, rather than the longest list of mobile features.