HVAC
No cooling / no heat
Capture location, broad symptom, urgency, contact details, and the approved booking or callback path.
Guided trade workflow demo
See how LOCKS AI adapts the front office to the trade.
The core workflow stays consistent across HVAC, plumbing, roofing, electrical, and other trades, while intake questions, urgency rules, booking logic, and escalation behavior are configured around the customer's operation.
Trade playbooks
Same operating layer. Different trade logic.
These are example workflow patterns. Production behavior is built and tested against the customer's actual service area, policies, systems, and escalation rules.
Plumbing
Leak / stoppage
Capture the customer, location, broad issue, urgency, and route the request without giving unsupported repair instructions.
Roofing
Storm / inspection lead
Capture property details, timing, broad concern, and route to the approved inspection, estimate, or sales follow-up process.
Detailed example · HVAC
After-hours no-cooling call
- Caller reports the AC is running but blowing warm air.
- Agent asks for ZIP code, caller name, callback number, and enough detail to route the request.
- Agent checks only approved service-area and scheduling rules.
- If a live calendar is unavailable, it creates a callback request instead of inventing an appointment.
- Owner receives a structured lead record and a clear next action.
Sample transcript
Caller: “My AC stopped cooling tonight.”
Agent: “I can help get that routed. What ZIP code are you in, and is the system completely off or still running?”
“78230. It is still running but the air is warm.”
“Thanks. May I get your name and best callback number? I’ll capture the issue for the service team. If approved appointment availability is connected I can offer it; otherwise this will be a callback request.”
“Yes, this is Jordan. 210-555-0148.”
“Thank you, Jordan. I have the no-cooling request for ZIP 78230 and your callback number. This is a callback request and not a confirmed appointment yet.”
Acceptance behavior
What the production version must prove.
These examples become part of the live QA matrix. The production agent does not launch for a customer until the full test set passes against that customer’s approved rules.
01
In-area HVAC lead
Capture name, phone, ZIP, issue, timing; route to connected calendar or callback.
02
Outside service area
Do not promise service. Capture the request only if policy allows and mark for human review.
03
Emergency / safety issue
Stop normal qualification and follow the approved emergency/escalation wording.
04
Unknown price question
Do not invent pricing. Explain that exact pricing requires the service team or an approved range.
05
No live calendar
Create a callback request; never say the appointment is confirmed.
06
Human requested
Transfer or notify the approved contact if available; otherwise capture a callback request.
Map your first revenue workflow.
Bring the trade, call flow, systems, and revenue leak. We will scope the smallest measurable workflow before broader automation.