Organize HVAC return-visit requests without guessing fault

Capture the report before classifying it

A commercial customer calls after a recent visit and says the building still feels warm. The office needs enough context to route the request, but should not diagnose it or decide responsibility from the caller’s wording. Gather the reported symptom in the customer’s own words, property, contact, time reported, prior job reference if verified and the established escalation route.

Use the company’s normal urgent-call procedure where applicable. AI should organize the intake evidence after those procedures are followed; it should never decide whether a condition is safe or advise a caller to operate equipment.

Separate links, statements and open questions

Ask for an intake table with a verified prior-job link, reported issue, customer request, available prior notes, uncertain relationship and reviewer. In a fictional case, the prior work concerns a north-wing unit while today’s caller mentions a south-wing room. Record both statements and leave the relationship unresolved. Do not label the visit a failed repair merely because dates are close.

Preserve technician findings as recorded. If the caller challenges a prior statement, show the two accounts separately. Avoid generating a definitive incident narrative that erases disagreement. A suggested reviewer question might ask which equipment served the affected area; it must not supply the answer.

Route a fact-based handoff

A dispatcher or service manager reviews the record and decides the next operational step. Warranty, pricing, credits, scheduling and accountability remain with their authorized owners. The assistant can prepare a concise internal handoff but cannot promise a free visit, book an appointment or blame a technician.

Try the process on fictional examples involving a clearly matched prior job, a different property and an uncertain equipment reference. Check whether the summary preserves each distinction. Review records reopened because of bad matching separately from requests that were correctly routed. Speed is useful only when the destination receives an accurate account of what is known.

Review before use

• Quote the reported issue accurately.
• Verify prior job and property separately.
• Leave cause, warranty and responsibility unresolved.
• Keep urgent-call and technical decisions with established staff.

Source context and limits

Jobber’s documentation provides context for recorded notes and attachments. The return-request routing table is our proposed office procedure, not automated diagnosis or a vendor-provided fault determination.