1. Map the field day
Choose representative service types, assigned roles, required records, and the office handoff. Review where technicians lose time today and which records your office needs to accept a completed job.
Field service software / In development
HVAC technician app for the complete service visit.
WhatNotDev is building a technician mobile app that connects the people on the job to the people running the office. Review assigned service calls, plan the day, capture findings, and send the next action back with the job context attached.
This page describes the current project and its development limits. Explore the workflows below, or ask for a walkthrough to review the actual build with your team.
Technician app · In developmentThe office has a CRM.
The office has a CRM.
Give the field a workspace.
We're building a connected HVAC technician app for the work between dispatch and completion. Jobs, schedules, customer details, and field notes, together on a phone.
- Today’s assigned jobs
- Day and week schedules
- Customer and service history
- Job status and work notes
WhatNotDev / Field service
Your day. In hand.
Connected to your HVAC CRM
Today's appointments
2 appointments · Sample schedule
09:00 AMOn site
Jordan Miller
AC diagnostic
11:30 AMScheduled
Alex Carter
Seasonal maintenance
Illustrative preview · Sample data
Who it is for
Built for the technician. Connected to the office.
Residential service, replacement, maintenance, and light commercial visits all involve a chain of information. The app keeps the field part of that chain close to the technician.
Technicians need an understandable day plan, customer context, a record of the work, and a clear next step. The app focuses on their assigned work instead of asking them to navigate an office dashboard on a phone.
Dispatchers and office staff need progress and useful findings, not another stream of unstructured messages. Linked job records bring notes, evidence, and recommendations back into the service workflow.
Owners and managers need clear responsibilities. The Custom Agentic CRM coordinates the wider operation, while financial decisions and completion requirements remain with their authorized roles.
01
Daily schedule and assigned jobs
A field technician needs a reliable answer to three questions: what is on today, where is the next call, and what does the office already know about it? The app brings those details into a workspace connected to the HVAC CRM.
- Today shows appointments for the device’s local date and separates earlier open calls from the current day’s schedule.
- Calendar supports day and week views, date selection, Previous, Next, and Today controls so the technician can review upcoming work.
- Jobs searches assigned work by customer, address, job number, and service type, with completed calls available as history.
- A Current Job bar helps return to underway work. When several calls are underway, the technician is asked to review them rather than being sent to an arbitrary job.
How this connects to the office
The office continues to own appointment confirmation and dispatch assignment. A technician’s work list reflects assigned jobs, rather than exposing the company’s entire customer or sales database.
02
Customer context before the visit
Open the job to review the service type, appointment, customer contact, location, reported problem, notes, and available service history. Known context stays with the service call instead of depending on a separate text conversation.
- Call the customer and open directions from the job. Navigation features are being developed alongside the field workflow.
- Read available site access and hazard notes so the visit starts with the information the office has recorded.
- Review captured booking details, including customer-reported symptoms and equipment information, where that intake exists.
- Keep customer-reported information separate from the technician’s findings and the work actually performed.
How this connects to the office
The job becomes a shared point of reference for the technician and dispatcher. Missing equipment, duration, or coverage details stay missing until someone records them; the app does not invent those facts.
03
Work states and completion checks
The app records field progress while preserving the CRM’s completion rules. En route, on site, and work records describe what is happening at the visit. A completed job requires more than a button tap.
- Arrival must precede completion, and completed jobs cannot be moved backwards through mobile status updates.
- Technicians can save work notes even when a completion attempt is blocked by missing records or an office requirement.
- The finish flow makes outstanding requirements visible. An incomplete outcome needs a reason and does not establish completion.
- Job progress remains separate from a customer’s approval of additional work or a change to the sales pipeline.
How this connects to the office
The office can review the same job context and outstanding requirements. A local or queued update is not presented as confirmed completion until the CRM accepts the required transition.
04
Parts, equipment, photos, and receipts
Field documentation needs to describe what was found, what was installed, and what is only being proposed. The current project includes materials, equipment observations, and evidence workflows with further device validation still in progress.
- Materials records distinguish installed, proposed, and returned quantities and can capture fractional quantities and units of measure.
- Known purchase costs and actual expenses can be recorded without turning an unknown cost into a guessed amount.
- Photos and receipts can be associated with the job, work stage, and relevant equipment, with upload and confirmation status.
- Original evidence is preserved, and confirmed files become available to authorized office staff for review.
How this connects to the office
A recorded material is not an automatic warehouse stock adjustment, supplier credit, or customer invoice. Those actions have separate office and integration requirements. Native camera, storage, and media handling still need physical-device acceptance checks.
05
Recommendations and office handoffs
A technician’s recommendation should arrive with enough context for the office to act on it. The handoff workflow connects a repair, replacement, or maintenance finding to its equipment, evidence, and proposed scope.
- Prepare a finding with up to three scoped options and the confirmed evidence available for that job.
- Keep a draft or queued submission on the device when connectivity is interrupted, with receipt confirmed only after the CRM accepts it.
- Office staff review the scope, confirm customer prices, and create an estimate in the existing estimates workflow.
- Track approval of an exact option, decline, or deferral with the authorized contact and evidence of the decision recorded by the office.
How this connects to the office
Customer self-service approvals, electronic signatures, and automatic delivery are not represented as complete features. Approved follow-up work still needs a confirmed appointment and dispatch assignment; a recommendation does not automatically complete the original job.
06
Offline records and reconnection
Signal can disappear in a basement, plant room, or remote service area. Offline resilience is being built around previously loaded jobs, durable field records, visible pending states, and a confirmed return path to the CRM.
- Previously loaded job details and supported field records can remain available when the connection drops.
- Notes, work states, supported materials, equipment observations, and evidence have storage and queue workflows in the current project.
- Pending Records distinguishes waiting items, items that need attention, and preserved unsent copies instead of silently discarding them.
- Record identities help prevent duplicate application, while version checks flag stale updates for attention instead of silently overwriting newer work.
How this connects to the office
Offline support is still being validated by record type and device. Some approvals, media flows, new site or equipment creation, and phone restart or locked-screen recovery need further integration or acceptance work. A local save does not mean the office has received the record.
Two connected workspaces
One operation. The right view for every role.
The CRM coordinates the business. The technician app carries the assigned work into the field. Together, they keep the handoff attached to the job.
| Workflow | Custom Agentic CRM | Technician App |
|---|---|---|
| Primary workspace | Owners, dispatchers, sales, and office teams | Technicians working on assigned service calls |
| Daily focus | Lead intake, dispatch, estimates, invoices, and operational oversight | Appointments, customer details, work records, and job progress |
| Information shared | Customer, service-call, equipment, and job history | The assigned job and the field records linked to it |
| Financial responsibility | Office review of scope, prices, estimates, and billing | Capture job findings, materials, and costs for authorized office review |
| AI scope | Optional agentic workflows designed and validated for your project | Core field tools work independently of planned AI assistance |
| Getting started | Discovery, workflow mapping, agreed scope, build, migration, and training | Review the current build, confirm field requirements, and plan a pilot |
Plan a practical rollout
Review the build. Prove the workflow. Then expand.
The technician app is in active development. Browser and API checks exist for several workflows; production availability and physical-device readiness are separate decisions to review with your team.
2. Validate a small pilot
Walk through a scheduled visit, customer context, work states, evidence, a recommendation, and an interrupted connection. Test the actual phones, permissions, and network conditions your team will use.
3. Agree the launch scope
Confirm supported devices, app distribution, deployment, training, integrations, support, and what remains in development. Expand only after the people handling dispatch and field work can complete the agreed workflow.
Standard and AI editions
The project includes Standard and AI edition identities. The current field tools remain available in both; live AI field assistance is not implemented. Optional AI workflows should be scoped and demonstrated separately, with their data sources and approval steps agreed before rollout.
Read about agentic CRM developmentFAQ
HVAC technician app questions
An HVAC technician app is a mobile workspace for assigned service calls, appointments, customer details, work notes, and field records. The WhatNotDev project connects those workflows to the office CRM so technicians and dispatchers work from linked job information. Read about the custom HVAC CRM that supports the wider operation.
The app is in active development and is not offered as a public store download on this website. Contact us to discuss the current build, a walkthrough, pilot requirements, and availability for your team.
Yes. The current project connects technician accounts to the CRM backend for assigned jobs, calendars, customer context, and field records. Each company’s deployment, permissions, integrations, and rollout need to be reviewed as part of its project.
The current project supports offline workflows for previously loaded jobs and several field record types, with pending records and reconnection sync. Coverage varies by feature and device, and native restart and locked-screen recovery still need validation. Completion is unconfirmed until the CRM validates the required records. Offline readiness is reviewed during a pilot.
The project includes job materials, installed/proposed/returned quantities, known costs, actual expenses, and evidence records with confirmation states. These records do not automatically adjust inventory or create customer invoice charges. Native camera and storage behavior still need physical-device acceptance checks.
The technician submits the finding, equipment context, evidence, and proposed options. Authorized office staff review the scope, confirm customer prices, and create an estimate. Customer decisions and approved follow-up bookings follow the office workflow rather than being inferred from a field note.
Live AI field assistance is not implemented in the current build. Standard and AI edition identities exist, and the currently available core field tools remain available in both. Optional agentic workflows can be discussed separately as part of a Custom Agentic CRM project.
The project is built with Expo and React Native for a mobile workflow, with a browser preview used during development. Store distribution, native device testing, hardware permissions, and supported devices must be confirmed before a team rollout. The website preview does not establish production readiness on either platform.
The technician app is the field workspace. Office dispatch, customer pricing, accounting, and management reporting belong to the wider CRM and its agreed integrations. We map which system owns each responsibility during discovery to avoid duplicate or conflicting records.
The phone panel on this page is an illustrative interactive preview with sample data. It explains the field workflow and does not sign in to your CRM. Ask for a walkthrough to see the current connected app build.
Cost depends on the field workflow, CRM integration, record types, device requirements, offline scope, migration, and support needed. We agree scope and pricing during discovery. There is no fixed public download price or self-service subscription checkout on this website.
Choose the service types and technicians to include, agree required job records, review device and connectivity needs, and walk through an office-to-field job. Verify a normal visit, a blocked completion, an offline record, and an office handoff before expanding the rollout. Tell us about your team to plan that review.
See the current project
Show us how your technicians work.
Tell us about your crew, service types, current CRM, devices, and the handoffs that cause delays. We will review the current app build against the field workflow you need.
Prefer to start with the office? Explore the custom HVAC CRM.