Dispatcher approval should be a recorded decision about a specific request. A message saying “looks good” in a busy chat is difficult to interpret when the customer later asks why a visit changed.
Define exactly what approval permits. It might authorize creating a job, choosing a visit window, assigning a technician, or overriding a service-area rule. Those actions should not inherit authorization from one vague approval flag.
Bind approval to the reviewed facts
Create an approval record with request identifier, request version, dispatcher identity, decision, scope, timestamp, and reason where required. Show the dispatcher the property, reported issue, proposed category, scheduling assumptions, and unresolved questions.
When material facts change, mark the old approval as stale. A visit approved for one address should not remain automatically approved after the caller changes towns. The same applies when the service scope or requested time changes.
Work through a fictional dispatch decision
An AI intake captures a water-heater inquiry at a residential property. The dispatcher approves a routine assessment tomorrow afternoon. Before the job is created, the caller explains that the property is a commercial building and requests tonight instead.
The workflow should preserve the original approval history but require a new decision for the changed request. Silently applying the old approval would authorize a different service under different operating conditions.
| Approval case | Required behavior |
|---|---|
| Approved request unchanged | Execute only approved scope |
| Dispatcher rejects request | Preserve reason and next owner |
| Address changes | Invalidate affected approval |
| Approval expires | Return to review queue |
| Two dispatchers disagree | Apply explicit conflict policy |
Separate approval from execution success
An approved action can still fail. Store the remote operation result independently from the dispatcher's decision. Staff need to distinguish “approved but not booked” from “booked and awaiting attendance.”
Use a controlled transition from pending review to approved, then to attempted and confirmed or failed. If execution times out, the action becomes uncertain and needs reconciliation. Repeated approval notifications must not trigger another job creation.
Formal approval adds friction, so reserve it for decisions that need human authority. Routine low-risk requests may follow preapproved rules instead. Even then, record the policy version that permitted the action so reviewers can explain the result.
Review appointment request states when aligning the internal approval queue with what the caller hears.
Questions about dispatcher approval
Is receiving a notification the same as approval?
No. Receipt, acknowledgment, and authorization are different events. Define which explicit action records approval.
Can approval happen over the phone?
Yes if the workflow records the approver, reviewed request version, decision, and authorized scope through the approved process.
What should a caller hear while approval is pending?
Explain that the request is with dispatch and give the agreed follow-up expectation. Do not describe the visit as confirmed until the required approval and scheduling result exist.