Do not invent approval, urgency, budget, or decision authority
AI can draft a clean handoff message, but it should not decide who is authorized, imply someone has approved the work, add pressure, or guess at budget. Keep the message factual: what was discussed, what needs review, what would help the decision maker, and what the next safe reply can be.
Human-review rule: an owner, manager, estimator, or approved sales lead should review any message that mentions price, financing, warranty, permit, insurance, contract terms, discounts, deposits, cancellation, emergency work, or final approval.
Copy/paste decision-maker handoff scripts
1) Spouse / partner review
Hi {first_name}, thanks for talking through the {service} estimate. If it helps, here is the short version to review with {decision_maker}: {scope_summary}. The next step is {approved_next_step}. Reply QUESTIONS if you want us to clarify anything before you decide.
2) Property owner approval
Hi {first_name}, I understand the property owner needs to review before scheduling. We do not want to assume approval. You can forward the estimate and this summary: {summary_for_owner}. If the owner has questions, we can answer them through {approved_contact_channel}.
3) Manager / committee review
Hi {first_name}, for manager or committee review, the key items are: scope {scope}, estimated timing {timing}, and open questions {open_questions}. We will keep the estimate open until {review_date_or_window}. Reply UPDATE when you know the next step.
4) Tenant or coordinator handoff
Hi {first_name}, since {approver_role} makes the final decision, we will not schedule work until approval is confirmed. Please share the estimate with them, and tell us who should receive scheduling or scope questions.
5) Budget-fit review without pressure
Hi {first_name}, if the estimate needs budget review, that is completely okay. We can answer questions about the included scope, timing, or options already discussed. We cannot add discounts or financing terms by text unless they are approved in writing.
6) Final helpful closeout
Hi {first_name}, one final check-in on the {service} estimate. Should we keep this open for {decision_maker_or_review_step}, answer a question, or close it for now? No pressure either way — we just want the job file to be accurate.
CRM fields to add before the next follow-up
- Decision maker: requester, spouse/partner, property owner, manager, committee, tenant coordinator, finance contact, unknown.
- Review blocker: price, scope, timing, access, permit/HOA, financing, insurance, owner approval, competing quote, missing detail.
- Approved next step: answer question, revise scope, send summary, schedule call, wait for review date, close out.
- Stop rule: escalate legal, insurance, permit, warranty, financing, discount, deposit, safety, dispute, or contract questions.
AI prompt for adapting the templates
You are helping a local service business draft decision-maker handoff text messages after an estimate. Use only the facts I provide. Do not invent approval status, price, discount, warranty, financing, permit, insurance, legal, deadline, availability, diagnosis, or decision authority. Keep each message under 480 characters, friendly, truthful, and easy to answer. Include variables in {double_braces}, one CRM note, and a human-review checklist before sending.
Related resources: quote follow-up templates, quote expiry reminders, and missing estimate detail templates.
Want the whole follow-up workflow?
The paid Local Lead Rescue System expands this into missed-call scripts, web-form follow-up, estimate follow-up, stale-lead recovery, CRM tags, and human-review rules for local service teams.
Product signal: if decision-maker handoff content earns clicks, replies, or prospect interest, add a decision-maker handoff worksheet to Local Lead Rescue buyer materials with approver-role fields, review-blocker labels, and manager approval stop rules.