A saved service request is the start of operational work, not proof that the customer’s issue was resolved. Track ownership and status changes through the staff workflow so intake metrics do not overstate the final outcome.
Request resolution needs a business definition
Resolution tracking follows a request from creation through the steps the business considers complete. Possible stages include acknowledged, assigned, quoted, scheduled, completed, cancelled, and closed unresolved. The exact model must reflect actual operations.
For a proposed design, give the request a stable identifier and retain its originating interaction references. Record status transitions, actor, time, reason, and next owner. Separate customer-request completion from notification delivery or dashboard viewing.
Do not allow an AI summary to mark work resolved without the authoritative operational evidence required by policy. A statement that the caller sounded satisfied is not proof that a technician attended or a quote was accepted.
Follow a fictional repair request
The receptionist saves a request about a leaking unit. Staff acknowledge it, assign an estimator, and send a quote. The customer declines the quote. The request can be closed under the business’s declined-work disposition, but it should not be reported as a completed repair.
Another request remains unassigned. Even if the intake was accurate, the customer has not received the next service step. The dashboard should surface the ownership gap rather than count the saved row as end-to-end success.
| Stage | Evidence to retain |
|---|---|
| Intake saved | Confirmed required fields and request reference |
| Assigned | Current accountable staff or queue |
| Quote sent | Authoritative quote state |
| Work completed | Defined operational completion evidence |
| Closed without service | Explicit reason and customer-facing disposition |
Use fixtures that skip or reverse stages to test the state rules. A reopened request should preserve history rather than creating a misleading second completed opportunity.
Report the funnel and elapsed time
Show how many requests reach each stage and how long they remain there. Separate the receptionist’s intake contribution from later staffing, pricing, and service-delivery effects. Those later outcomes matter, but they are not solely caused by the phone agent.
Detailed status models can burden staff. Use the minimum stages that change action or reporting, and make ownership obvious. Integrate existing authoritative systems where possible instead of requiring duplicate manual updates.
This tracking design is proposed. The HVAC operations case study documents requests, quotes, and follow-up tracking without claiming automated dispatch or measured business results. Read callback ownership.
Request resolution FAQ
Is a saved request a resolved customer problem?
No. It establishes intake, with later operational stages still outstanding.
Should declined quotes count as completed service?
Keep a separate closed-without-service disposition under the business definition.
Who should update resolution status?
The authorised operational actor or authoritative integration responsible for that real-world step.