Once the reminder sequence is done, the next question is classification. A landscaping company cannot send the crew back to the property with a note that only says "customer did not respond." The route needs to know whether the affected area is excluded, still under review, or ready for approved return work.
This matters because silence is not approval, but silence also should not freeze the entire route. The office needs a clean final state before the next visit.
Close the area as excluded when the customer had a clear revised estimate, the follow-up sequence is complete, and normal service can continue around the held area. Keep it in still-needs-review only when there is a real unresolved judgment issue: safety, access, boundary confusion, pricing uncertainty, or a customer signal that changes the scope.
If the revised estimate was sent clearly and the customer never responded, the company should not keep the held area floating forever. The route team needs to know that the affected area is outside the approved service scope.
Excluded does not mean the customer is banned from reopening the request. It means the crew should not treat that area as part of the next normal service visit until the customer approves or asks for another review.
| Final state | Use it when | Route meaning | Reopen trigger |
|---|---|---|---|
| Excluded | The estimate was sent, follow-up completed, no approval or question came back, and the boundary is clear | Continue approved service; do not service the held area | Customer approves, declines with a different request, or asks to revisit the scope |
| Still needs review | There is real uncertainty about access, safety, affected-area boundaries, pricing, or customer intent | Hold the affected area and route the question to the owner, estimator, or office before promising work | Office resolves the judgment issue and converts it to approved return work or excluded |
| Approved return work | The customer approved the revised estimate or a corrected scope before the next visit | Schedule or assign the approved return task under its own work order | Not applicable; the scope is no longer a no-response item |
Still-needs-review should be a real operational state, not a softer way to avoid closing the loop. If every no-response estimate stays in review, the next crew inherits stale ambiguity and the office has to rediscover the same facts later.
Use still-needs-review when the business actually needs one more decision before excluding or approving the area. Otherwise, excluded is cleaner, safer, and easier for the route to follow.
Ask one question: Would the next crew be at risk of making a bad promise or touching the wrong area if this is marked excluded? If yes, keep it in review and assign an owner. If no, close it as excluded and tell the route exactly what may continue.
The first line of the note should be the final state, not the full history. The history still matters, but the crew needs the action boundary first.
| Classification | Recommended route note | Why it works |
|---|---|---|
| Excluded | "No-response closeout complete. Back-right drainage bed excluded from normal service. Continue approved front, side, and standard maintenance only. Reopen only if customer approves revised estimate or asks office for review." | It tells the crew what not to touch and what can continue |
| Still needs review | "Back-right drainage bed still needs office/estimator review before route work. Do not promise return work. Continue approved areas only and route customer questions to estimator." | It preserves the unresolved judgment without freezing unrelated service |
| Approved return work | "Customer approved revised drainage-bed scope. Return work must be scheduled under approved estimate/work order; do not blend into normal maintenance visit unless assigned." | It prevents approved project work from being absorbed into routine service |
If the area is excluded, the customer message should say normal approved service can continue but the held area will not be serviced unless they reopen or approve the revised estimate.
If the area still needs review, the message should say the company is holding that area for office or estimator judgment and will avoid promising work there until the question is resolved.
"Since we did not hear back on the revised estimate, we will keep the held area out of normal service for now. We can continue the approved maintenance areas, and we can reopen the held area if you approve the revised scope or want us to review it again."
"We are keeping the affected area in review before promising route work there. Normal approved service can continue around it, but the office/estimator needs to confirm the next step before the crew returns to that area."
An AI receptionist should not invent the final classification. It should capture and repeat the state the office has already chosen: excluded, still-needs-review, or approved return work.
The useful AI handoff is structured: affected area, revised estimate status, follow-up sequence completed, final classification, allowed route work, reopen trigger, and owner for any unresolved review. That gives the next caller a clear answer without forcing the office to reread a stale thread.
Status: no-response closeout complete. Classification: excluded. Affected area: back-right drainage bed. Allowed route work: approved front, side, and standard maintenance only. Reopen trigger: customer approves revised estimate or requests another review. Owner if reopened: estimator.
ServiceVoice AI helps landscaping companies answer calls, capture the right details, and keep route-ready service separate from quote-heavy project decisions.