A customer add-on request during a separate late-approved return visit should not sit in a vague middle state. Once the crew captures the request, the office has to classify it before anyone promises price, timing, or completion.
The classification matters because each path protects a different promise. A revised return-work order protects the current approved return. A new estimate protects pricing and project judgment. A future route note protects recurring-service context without pretending there is a new approved job.
A while-you-are-here landscaping add-on should become a revised return-work order only when it is tightly connected to the same approved return scope and can be reviewed, priced, and scheduled under that return promise. It should become a new estimate when it changes area, materials, labor, design judgment, access, or price. It should become a future route note only when it is minor recurring-service context that does not require separate approval or completion.
The worst outcome is not telling the customer no. The worst outcome is letting the customer, crew, office, and estimator all believe a different promise was made.
After a late-return add-on request, the office should assign one label and one next owner. That label should show up in the customer update, crew note, and follow-up task.
| Classification | Use it when | Do not use it when | Owner |
|---|---|---|---|
| Revised return-work order | The request is attached to the same affected area, same return visit, same crew capability, and a clear approved price or scope update | The request creates a new area, new material need, unclear price, or project-level judgment | Office or estimator revises the return-work order before crew execution |
| New estimate | The request changes scope, labor, materials, irrigation, drainage, planting, cleanup volume, access, or design decision-making | The request is only a small recurring-service reminder with no price or completion promise | Estimator owns pricing, scope, and customer approval |
| Future route note | The request is low-risk service context for the next normal visit, with no separate price, materials, or project promise | The customer expects the added work to be completed as a stand-alone task | Route scheduler or crew lead adds it to normal-service notes |
The office does not need a long meeting. It needs a test that prevents field improvisation from becoming company policy.
One: Is the added work inside the same approved return area and customer promise? Two: Can price, time, materials, and crew fit be confirmed before work starts? Three: Would a customer reasonably expect separate completion if this note appears on a route sheet?
If the first two answers are yes, revise the return-work order. If the third answer is yes and the first two are not clean, create a new estimate. If the answer is no because the request is only normal-service context, use a future route note.
A revised return-work order is for add-ons that still belong to the current late-return decision. The office can update the approved scope, confirm the price or no-charge boundary, and tell the crew exactly what changed.
Examples include a small adjacent cleanup inside the same affected bed, a minor extra trim that uses the same crew time already approved, or a clarification that the original return included one additional edge or corner.
"Customer requested added cleanup along the same side-yard return area. Estimator approved revised return-work order: add the listed two-foot section only. Price/scope confirmed by office. Do not expand beyond side-yard return area."
A new estimate is the right path when the add-on request creates a separate buying decision. The customer may still want it quickly, but speed does not remove the need to price and approve it correctly.
Use this path for extra irrigation checks, drainage changes, planting, removals, hardscape-related work, larger cleanup areas, tree work, material decisions, or anything that could affect crew time beyond the approved return.
| Customer asks for | Why it needs a new estimate | Customer update |
|---|---|---|
| "Can you also handle the back corner cleanup?" | New affected area and labor volume outside the approved return | "We captured that as a separate estimate request so we can price and schedule it correctly." |
| "Can you fix this irrigation issue while you are here?" | Diagnostic and material risk that may change scope and parts | "That irrigation request needs estimator review before we promise the repair." |
| "Can you add plants in this section too?" | Materials, design choice, and price approval are not covered by the return | "We will separate the planting request into its own estimate instead of adding it to today's return." |
A future route note is for context, not for unpaid project work. It works when the request is a normal-service reminder that does not need a quote, special materials, or a stand-alone completion promise.
Good future-route notes sound like: watch the side gate latch, check the back corner next visit, trim this recurring-service edge if normal timing allows, or confirm the customer moved patio items before the next maintenance stop.
If the customer would be upset because the request was not completed as a separate job, it is not just a route note. It needs revised return-work-order approval or a new estimate.
An AI receptionist should not bury the request in a generic message. The handoff should ask the office to classify the add-on as revised return-work order, new estimate, or future route note.
The useful intake captures the approved return-work order, the new requested work, affected area, whether the crew is still on site, materials or access risk, customer urgency, and which owner should make the classification.
Late-return add-on classification needed: customer asked for back-corner cleanup while crew was on site for approved side-yard cleanup return. Approved return: side yard only. Likely path: new estimate because the request adds a separate area and labor. Owner: estimator to confirm price and schedule before customer promise.
A separate late-approved return visit should end with a clean state, not a new gray area. The crew captures the request. The office assigns the label. The customer receives the next-step update. The crew note reflects only approved work.
That keeps the company helpful without training customers to treat every crew arrival as a chance to renegotiate scope at the curb.
ServiceVoice AI helps landscaping companies answer calls, capture the right details, and keep route-ready service separate from quote-heavy project decisions.