How should a service plan track visits that are still owed?
Format: Article.
Start with the visits promised in the customer's approved plan. Give each one a record. Link it to any appointment and checked work report. Do not subtract a visit just because someone put it on the calendar.
The office needs to answer three different questions: What does this plan provide? What has been scheduled? What evidence shows the relevant visit was completed? When the answers disagree, create a review item rather than silently changing the balance.
Microsoft says Field Service agreements can create work orders that repeat on set dates.[9] That is a software feature. It does not prove what a customer is owed. Check the approved plan terms and service records to find that answer.
Begin with the plan, not the calendar
Keep the plan ID, version, customer, covered property and effective period. Link the actual approved terms. Ask the plan owner to identify the promised visit types and any conditions that affect how visits count.
Do not assume all plans offer the same number or type of visits. Check how often they are due and what happens if one is missed or canceled. A renewed plan may have new terms. List each covered property or unit before the office counts visits.
If the terms are unclear, show “plan terms need review.” Do not show a firm balance based on guesses. Ask the plan owner to resolve the question through the company's process. “Entitlement” here means what the plan says the customer is owed.
Use separate states for each visit obligation
The following table is a proposed administrative model. The company must adapt it to its actual plan terms and review roles.
| State | Evidence needed | What it does not prove |
|---|---|---|
| Terms confirmed | Approved plan version and staff review | Any visit has occurred |
| Due for planning | Visit requirement linked to those terms | A customer appointment exists |
| Proposed | Suggested date or contact attempt | Customer or dispatch confirmation |
| Scheduled | Reviewed appointment record | Completed service |
| Visit record received | Technician's submitted record | The visit counts under the plan |
| Completion checked | Authorized review of required evidence | Unrelated obligations are complete |
| Exception open | Missed, partial or disputed visit with owner | Entitlement has been removed |
Each promised visit is an obligation: work the plan calls for. Link its ID to the appointment and work report. If the date changes, keep the appointment history. Do not create a second promised visit. Ask the plan owner how a return trip counts.
Review missed visits without erasing them
Create a queue for obligations whose expected window has passed without checked completion. Give each row the last known appointment, the source of the current state, the unresolved question and a follow-up owner.
Ask whether the visit was never scheduled, was canceled, was attempted without completion or has a missing closeout record. Those are different office tasks. One needs scheduling, another needs customer contact, and another needs evidence from the service team.
Record the next review time as an internal task target, not a promise to the customer. Messages about remaining visits should use reviewed terms and approved wording. Do not let an overdue badge imply a refund, extension or waiver.
Hypothetical example: one complete visit and one missed slot
A fictional annual plan provides two specified visits during its stated period. The first has a checked work record. The second has an appointment marked canceled after an access problem. There is no completed service record for that obligation.
The office shows the first obligation as complete and the second as an open exception. It does not label the plan “fully used” because two dates appeared on the calendar. It also does not promise that the missed visit rolls into the next period.
The plan owner reviews the actual terms and the recorded access issue. The scheduler receives a task to arrange the next approved step, with customer contact subject to the office's review rules. Until that decision is recorded, the remaining obligation stays visible.
A later appointment links back to the same promised visit. Staff check the work report before marking it complete. This example shows how to match records. It does not set terms for real plans or decide a customer's rights.
Check the balance from both directions
Start with every obligation in the approved plan and ask what happened to it. Then start with every visit linked to the plan and ask which obligation it serves. This catches unlinked work records as well as promises with no appointment.
Keep corrections traceable. If staff find that a completed record belongs to a different property, remove the incorrect association through the approved correction process and reopen the review. Do not delete the evidence or quietly adjust a total.
A useful management view separates confirmed remaining visits from unresolved entitlement questions. A single number can hide the very cases that need attention.
Core Agentic can discuss a custom view that matches plan records to checked visits. We are not showing a live link to your plan software. Book a Demo to discuss a visit list that shows what is complete, what is still owed and what staff must resolve.
Sources
These sources describe the named provider or framework. They do not establish a Core Agentic integration, customer result or certification.