A tech goes out, looks at the system, and recommends work. The moment the homeowner says yes to one of those recommendations, it stops being a recommendation and becomes a job somebody has to go and do. That handoff is where work gets lost. This is the thing that catches it.
A tech goes to the house once and does all of it. Approve three things on one visit and you get one Service Order carrying all three — and re-approving something already dispatched reactivates it instead of raising a duplicate.
The call-by time and the visit window are computed once, when the homeowner says yes, and then stored. They are never recomputed — otherwise the promise you made quietly slides forward a day at a time while nobody notices.
The page counts approvals that never reached a Service Order and says so at the top: the homeowner said yes and nobody was asked to schedule it. One click routes them. It is the report you hope reads zero.
Normal, High — this week, URGENT — call today, EMERGENCY — call now. A line the rep flagged critical on the visit raises the whole order's urgency by itself, so it cannot be filed behind routine work.
An unanswered question from the field to the office is re-raised every six hours for three days. Then it stops pretending and logs that somebody needs to pick up the phone.
An office routes its service work to the parent company one job at a time. If that handoff fails, the job stays at the office with an error on the record — it is never silently dropped between two companies.
Service Orders are on every plan, including Starter.
Get a personalized demo of Sun Service CRM for your team.