Back to ServiceVoice AI

How should a landscaping company classify a new customer change after a clean late reopened-hold replacement confirmation and crew note?

Use this page when a late reply cleanly reopened one held customer-change item, the office sent the replacement customer confirmation and crew note, and the customer then changes scope, access, timing, price, or priority again. The new request is not a continuation of the clean reopen. It is a separate office decision while the freshly issued replacement note remains the live field baseline.

Short answer

Log the new request against the exact reopened item, preserve the current dated replacement note, and classify the new request before any customer promise or crew change. State whether the result leaves the note unchanged, replaces it, or holds route release.

Start with the active instruction—not the newest text thread

The clean-reopen decision was narrow: it restored one exact held item. It did not authorize the customer or crew to reopen older scope, attach new work, alter access, move the route, negotiate price, or take priority from another customer. Treat the latest dated replacement note as the source of truth until the office writes a newer one.

What the customer changesClassificationEffect on the active replacement note
A detail already inside approved scope, with no price, access, or route impactIn-scope clarificationLeave it active or issue a narrow dated clarification.
Area, task, material, or labor outside the reopened itemRevised return-work order or new estimateKeep the existing note active for approved work only; do not add the request in the field.
Gate, contact, weather window, availability, or route-day conditionAccess/timing review or holdScope can remain approved, but route release waits for the new condition.
Discount, price dispute, rush request, or move-ahead requestPrice/priority or owner reviewNo price, priority, or schedule promise; the replacement note remains unchanged.

Give the office a three-part decision

Every classification should answer three questions: what is the new request, what remains authorized now, and what must happen before anything changes? That creates one answer a customer can understand and one route-safe instruction the crew can follow.

Customer acknowledgement

“Thanks—we received your new request about [scope/access/timing/price/priority]. The current confirmation for [exact reopened item] remains in effect while we review this separately. We will confirm in writing if a new instruction, estimate, or route window is approved. Please do not rely on the prior message for this new request.”

Crew-note boundary

Active dated replacement instruction: [exact reopened item, authorized scope, access, timing, and route status]. New customer request: [brief label] is under office classification. Do not add, remove, reprioritize, reprice, or reschedule work from the customer conversation. Pause and contact the office if the request appears on site. A newer dated note is required before this instruction changes.

Do not collapse review, approval, and route release

An office review is not approval. An approved estimate is not a route release. A route release does not authorize unrelated work. Keeping those three states separate prevents a customer from hearing “we are looking into it” as a promise and prevents a crew from treating a text exchange as a job change.

What the AI receptionist should capture

Capture the active replacement-note date and exact reopened item; the customer’s request in their words; whether it affects scope, access, timing, price, or priority; photos or site-review need; desired deadline; and whether the customer is asking the crew to decide on site. Route the handoff to the right owner with a clear never-promise rule: no commitment until the office issues the newer dated instruction.

Want cleaner landscaping follow-up and route handoffs?

ServiceVoice AI helps landscaping companies capture the right details and keep route-ready instructions separate from quote-heavy or changed-work decisions.

See the Core Kit