Back to ServiceVoice AI

What should the customer update and crew note say after the office classifies a new customer change that arrived after a clean late response reopened an after-replacement no-response hold or closeout and a replacement note was sent?

This is the messaging control point after a clean late reply reopened an after-replacement no-response hold or closeout, the office issued a replacement confirmation and crew note, and the customer changed scope, access, timing, price, or priority again.

Short answer

Use one office classification in both messages. Tell the customer what is approved, pending, held, excluded, or under review; tell the crew only what is authorized in the field now. The dated replacement note stays controlling until a newer dated office instruction replaces it.

Start with the live instruction, not the newest text

The new customer request should be acknowledged, but it is not a field order. Both messages should anchor to the exact replacement note that became active after the clean late response, then state what the newest classification changes—if anything.

Message elementCustomer updateCrew note
Active baselineName the prior replacement confirmation and what still stands.Name the dated replacement crew note as the source of truth.
New requestDescribe it as reviewed, not automatically approved.Label it pending, held, excluded, or approved only as classified.
Next actionState estimate, access, timing, price, priority, owner, or closeout path.List permitted work and the stop rule for changed work.

Use clear classification language

ClassificationCustomer-safe wordingCrew-safe wording
No-impact clarification“The current replacement plan remains in place; we recorded your clarification.”“Complete active dated scope. Clarification does not change scope, price, timing, or priority.”
Revised return-work order“We are issuing a revised work order before the change is added.”“Do not perform the changed portion until the dated revised order is attached.”
New estimate or owner review“Your new request needs review before price, timing, or performance can be confirmed.”“Exclude new request; perform only approved replacement scope.”
Access, timing, price, or priority hold“The affected work is on hold while we confirm the condition.”“No route, price, or priority change without a new dated office note.”
Customer update template

“We reviewed your request about [new change]. Classification: [label]. The replacement confirmation dated [date] remains active for [approved scope]. [Pending/held/excluded] work: [plain description]. Next step: [estimate/access/timing/price/priority/owner review]. We will confirm any approved change in writing before it is added to the crew plan.”

Crew-note template

“Active instruction: [dated replacement scope and route condition]. Classification of new customer request: [label]. Authorized today: [exact work]. Do not [add/remove/reprice/reprioritize/reschedule] [new request]. If asked in the field, pause and contact the office. Only a newer dated office note replaces this instruction.”

Keep the promise separate from the route release

An estimate review, a friendly customer acknowledgment, or a price discussion is not permission to alter the route. The office should release the affected work only after the approved scope, access, timing, and price all match the new dated note.

What an AI receptionist should capture

Capture: property, active replacement-note date, customer wording, requested change, access constraints, deadline, photos or site-review need, and price or priority issue. Route: the correct office classification. Never promise: an added task, new price, moved route position, or crew action before the dated replacement note is updated.