The next visit should start with the last one.
This workflow shows a repeat customer record carrying site, equipment, agreement, past work, and a human-owned renewal or follow-up task into the next visit.
Office manager or technician · HVAC · a repeat customer calls before maintenance or additional work
What happens today
Today the office searches old notes and the technician arrives without equipment or agreement context.
Why it matters
The risk is a blank-slate visit, inconsistent follow-up, and a renewal or replacement conversation that depends on memory.
Where this starts
An existing customer has prior work, equipment history, and an agreement or service context the business is permitted to use.
The workflow
- 1The office finds the existing customer and site instead of creating a duplicate.
- 2The technician opens permitted equipment, past-service, agreement, and SOP context before work begins.
- 3Maintenance creates a distinct finding when additional work may be needed; it does not silently become a charge.
- 4If a proposal is appropriate, approved options and applicable pricing rules are presented for customer review.
- 5A renewal or follow-up item enters a human-owned queue, and the owner can review the linked timeline.
Where a person decides
A person decides whether to present additional work, send outreach, or apply any agreement rule.
If it does not go to plan
If an agreement is expired, consent is absent, the record is duplicated, or the customer declines, the system holds the appropriate exception. No automatic outreach or charge occurs.
Where this ends
Customer history, current work, an optional estimate, and the next follow-up are connected in one visible story.
What you can see
Customer and equipment timeline, job packet, optional estimate state, and renewal queue, using seeded demo data.
Why that is useful
The office and field team begin with context the customer has already provided.
What this does not claim. No renewal, repeat booking, replacement, consent, or stored-card autopay result is guaranteed.
Workflow reviewed 2026-08-13