No heat and no cooling are descriptions of a service problem, not diagnoses. An HVAC receptionist should collect the facts dispatch needs while avoiding a promise about the fault, repair price, or arrival time.
Start by confirming the service property, callback route, and whether the caller is asking about heating or cooling. Then ask the business's approved questions about the affected area and any reported concern that changes its escalation policy.
Keep urgency separate from technical diagnosis
The business must define how it handles urgent concerns and what language the agent uses. Do not ask the model to invent a safety assessment from a short call. If the caller reports a concern covered by the approved escalation script, follow that script and route appropriately.
Record reported conditions in the caller's terms. “No heat upstairs” is useful. “Failed ignition assembly” is an unsupported conclusion unless established through an authorized technical process outside intake.
Work through two fictional calls
One caller says the downstairs cooling system blows warm air but the upstairs system works. Another reports no heat throughout a rental property. Both need the correct property and equipment location recorded, but their dispatch categories and follow-up policy may differ.
For the rental call, clarify the caller's role and authorized contact route. For the cooling call, preserve which area is affected. The agent should not assume that a working second system makes the request unimportant or that every no-heat call requires the same response.
| Intake case | Required handoff fact |
|---|---|
| No heat throughout property | Affected scope and reported conditions |
| Cooling issue in one zone | Specific zone or equipment location |
| Existing open service job | Related job candidate for staff review |
| Caller reports urgent concern | Approved escalation path and result |
| No available visit window | Owned callback request without promise |
Read back the operational commitment
End with the service address, reported issue, and actual next step. If dispatch must review the request, say so. If a visit is confirmed through the approved system, state the correct date and arrival window.
Short intake improves call handling but can omit facts technicians need. Long questionnaires can frustrate callers and delay escalation. Ask only questions that change routing, preparation, or the next approved action; staff can gather technical detail later.
Use the HVAC project context to frame the workflow, then validate it with the business's dispatch lead and fictional calls.
Questions about no-heat intake
Should the agent troubleshoot the equipment?
Only use explicitly approved administrative or operational guidance within the agreed scope. Do not turn intake into improvised repair instruction.
Can the agent mark every no-cooling request urgent?
Follow the business's documented policy and retain the caller's reported facts. Blanket urgency can make the dispatch queue less useful.
What if the caller wants a guaranteed arrival time?
Give only a commitment supported by the scheduling and dispatch process. If staff must confirm, preserve that boundary and the callback expectation.