Service-job memory for HVAC companies
A repeat customer calls because the same room is too warm again. Someone remembers discussing a replacement last summer, but the details are in an old email. A technician needs to know what the customer actually reported and what was said about the options.
Provenience could make each service job's communication easier to find and check. Those records could also become the foundation for a longer customer service history.
Start with one service job
Treat a repair, replacement, or installation as a bounded project. Give it a roster covering the customer, office staff, and relevant collaborators. The business's shared Site contact captures its communication; a dedicated job contact is optional.
Capture what reaches those channels. A conversation on a technician's personal number will not appear automatically, and equipment telemetry is not something the communication pipeline diagnoses.
Bring in
- Customer calls, texts, and email describing symptoms and priorities.
- Conversations about repair options, replacement choices, estimates, and scheduling expectations.
- A technician's emailed recap of what was observed and discussed.
- Photos, manuals, and estimate attachments as cataloged files. For SMS/MMS, qualifying photos and short PDFs can be considered with their message; this does not make a manual or estimate an authoritative interpretation.
A connected service-management system could supply reference rows through a read-only connector. Support depends on the connector that can be built; there is no promised vendor list.
Ask
- What symptoms did the customer describe on this job?
- Which repair or replacement options did we discuss?
- What estimate amounts were stated, and were they tentative or firm?
- Where did the customer express a preference or agree to a next step?
The result should lead back to the source conversation. A generated briefing can help a business administrator prepare; a qualified person still decides the diagnosis and the work to perform.
Why the history matters
In a fictional service job, a customer asks for the least expensive repair during the first call. In a later email they say they want to compare replacement options before proceeding. Keeping both records prevents the office from treating the initial preference as the whole story.
At close-out, the planned review could connect stated estimates and expectations to recorded actual outcomes. A connected invoice would be reference evidence, not an extracted customer statement.
Extend toward repeat-customer history
A future customer-history application could bring together earlier service jobs before the next visit. Each visit would retain its own communication and sources.
Linking visits to stable customer, property, and equipment records still needs further design. Phase 1 provides the planned per-project evidence; it does not yet specify a complete longitudinal equipment record or a universal search by customer across visits.
Automatic diagnoses, dispatching, equipment monitoring, and write-back to service software are outside this idea's Phase 1 scope. Queries are for a business administrator; technician-scoped roles and customer portals are deferred.
Explore the platform model, see review and close-out, or discuss an early pilot.