Separate an unfilled appointment from a failed visit
Format: Company perspective.
A blank completion field does not tell you why a visit did not happen. No one may have been assigned. The customer may have canceled. The note may simply be late. Check before you judge the work.
Microsoft tracks work orders and bookings through separate stages. A booking's state can affect the work order's status.[10] Check those records and their history. One summary label may not explain what happened.
Choose a reason from the evidence
Use this proposed guide for schedule review. The labels are not proof on their own.
- No assignment: The dispatcher checks the assignment history. Use this reason only when it shows that the slot was left unfilled.
- Access failure: The technician or supervisor supplies a visit report. It must describe the attempted visit and the access problem.
- Customer cancellation: The office contact owner checks the cancellation message or contact note.
- Unknown cause: The reviewer cannot establish a reason from the records. Keep it unknown until there is evidence.
Also record what happened: an unfilled slot, an attempted visit, a canceled appointment or an open question. A reason code should not hide that difference.
Check the history, not just today's field
In this hypothetical example, a visit has no completion note. The dispatcher checks the slot's history. It shows that no technician was assigned. There is no conflicting visit report. The reviewer records “unfilled slot, no assignment.”
If the history were missing, the cause would stay unknown. A blank field would not justify blaming the technician or customer.
New evidence may change the reason. Keep the earlier entry. Add the new source, the reviewer and why the record changed. Do not quietly rewrite a performance report.
Core Agentic can discuss a custom schedule-review view with evidence and an owner beside each open issue. Book a Demo to discuss reason codes your team can check.
Sources
These sources describe the named provider or framework. They do not establish a Core Agentic integration, customer result or certification.