Build an HVAC missed-visit recovery queue with clear ownership

Confirm the appointment state before recovery

Choose a bounded set of commercial visits whose expected dates have passed. Gather visit ID, property, appointment window, assigned owner, recorded status and last verified note. Ask AI to separate confirmed uncompleted visits from cancellations, postponements and records whose completion evidence has not yet synchronized. Keep the original status wording.

This workflow starts after a specific appointment exception is identified. It is not an audit of every agreement visit and does not infer breach, customer fault or missed contractual obligations. Use the organization’s normal urgent-service procedure for active concerns; a generated queue must not delay an established escalation.

Work through three fictional exceptions

Visit A has a documented customer postponement but no agreed replacement window. Its next step is an account-owner timing question. Visit B shows a technician’s local completion note that the office cannot yet verify; its next step is record reconciliation. Visit C is explicitly marked uncompleted because access was unavailable; its next step is an access-owner review before a dispatcher offers another visit.

Do not collapse all three into a missed-service reminder. Use columns for verified state, source/date, customer impact as actually reported, missing prerequisite, responsible person, next action and due review time. A proposed next step is separate from a booked appointment or a delivered customer notice.

Resolve the prerequisite before offering a slot

Have the dispatcher check operational availability and the account owner confirm customer communication. Where access caused the problem, ask who must confirm access and by when. Where records are incomplete, verify the work history before offering a duplicate service visit. Keep credits, agreement interpretation and commercial concessions with their authorized owners.

After a person agrees the recovery action, record its actual state: awaiting contact, offered, customer-confirmed, scheduled or closed with evidence. Do not mark a row resolved simply because a draft message exists. Review the queue daily while it is in use and preserve changes in the source system. Measure time to a verified next step and duplicate-visit errors, not hypothetical customer retention or recovered revenue.

Release checklist

• Verify the state and source of each exception.
• Separate synchronization gaps from genuinely uncompleted visits.
• Assign an owner to the missing prerequisite.
• Record offered and customer-confirmed timing independently.

Source context and limits

Jobber documents visits as appointments linked to jobs. This recovery queue is our proposed administrative process, not a product guarantee or a determination that an agreement was breached.