After a reopened late-return add-on is scheduled separately, a customer may change scope, timing, access, or priority before the crew returns. The office can classify that change, but the next customer update and crew note have to carry the classification cleanly.
The goal is to keep the customer informed without turning the changed request into an unpriced crew-level promise.
After classifying a changed reopened add-on, the customer update and crew note should both use the same label: original return still valid, revised return-work order needed, new estimate needed, or hold/reschedule. The customer should hear what is approved and who owns the next step. The crew should see the active return boundary, the change label, and a clear instruction not to expand scope unless the office attaches the revised work order.
The biggest mistake is telling the customer one thing and leaving the crew with a vague note like "customer changed request." Use the same classification in the customer-facing update and the crew-facing note so the work order, route plan, and follow-up owner all match.
| Classification | Customer message job | Crew note job |
|---|---|---|
| Original return still valid | Confirm the update was received but did not change the approved return | Complete only the original separate return-work order |
| Revised return-work order needed | Explain that the connected change needs office or estimator confirmation before the return instruction changes | Wait for revised scope, price, materials, and owner approval before expanding work |
| New estimate needed | Separate the new request from the active return and set a review path | Do not perform the added work during the return visit |
| Hold or reschedule | Explain the timing, access, material, or capacity issue before promising a new window | Do not dispatch or proceed until the office updates the return status |
"Thanks for the update. We reviewed it against the reopened add-on that is already scheduled as a separate return-work order. Your update does not change the approved scope, timing, access, or price, so the crew will complete the original approved return for [scope/area] as scheduled. Any additional work would still need a separate office review."
Classification: original return still valid. Customer update reviewed; no approved change to scope, timing, access, or price. Complete only [original approved scope/area] under the separate return-work order. Do not add work or change priority from field conversation.
This label fits when the change is tied to the same affected area or task, but it still changes the field instruction enough that the original return note is no longer precise.
"We received your change to [changed detail]. Because this is connected to the reopened return but changes the crew instruction, we are holding the change for office/estimator review before updating the return-work order. The crew will only receive the revised instruction after the scope, price, materials, and timing are confirmed."
Classification: revised return-work order needed. Original return: [scope/area]. Customer requested: [changed detail]. Do not expand beyond the original approved scope unless revised return-work-order note is attached with office/estimator approval, price/material status, and updated completion boundary.
A new estimate is cleaner when the customer adds a new area, new material, irrigation or drainage judgment, design choice, uncertain labor, or a price/timing promise that does not belong to the active return.
"That added request is separate from the reopened return-work order already scheduled for [approved scope]. We are keeping the original return limited to the approved work and sending the new request through estimate review before we promise price, timing, or crew completion."
Classification: new estimate needed. Complete only [original approved return scope]. Customer's added request for [new work] is excluded from this return visit and routed to estimate review. Do not price, promise, or perform the new work in the field.
Hold or reschedule is the right label when the changed timing, access, materials, customer availability, or route priority means the return may not be executable under the confirmed plan.
"Because the latest update changes [timing/access/materials/priority], we need to confirm the return plan before sending the crew. We are holding the separate return-work order until the office confirms the new access condition, crew capacity, materials, and return window."
Classification: hold/reschedule. Do not dispatch or proceed under the prior return instruction until office updates [access/timing/material/route condition]. Customer change received: [detail]. Office owner: [name/role].
The AI receptionist should preserve the classification instead of writing a generic callback note. The handoff should make it obvious which promise is active, which part changed, and who owns the next action.
Active state: reopened no-response late-return add-on scheduled as separate return-work order. Original approved scope: [scope/area]. Customer change: [exact wording]. Office classification: [original still valid / revised return needed / new estimate needed / hold-reschedule]. Customer update needed: [message label]. Crew note needed: [field boundary]. Owner: [office/estimator/scheduler].
Every changed reopened add-on message should answer four questions: what was originally approved, what changed, what label the office assigned, and what the crew is allowed to do now.
If those four answers are visible in both the customer update and the crew note, the landscaping company can stay responsive without letting a late-return recovery turn into scope creep.
ServiceVoice AI helps landscaping companies answer calls, capture the right details, and keep route-ready service separate from quote-heavy project decisions.