Estimate follow up

Who this role is for

This lane is for sales or service teams that already issue approved estimates but lack a consistent record of customer response and next action.

It works when each proposal has an owner, validity details, approved follow-up wording, and a clear route for pricing and technical questions.

The problem it addresses

An estimate can stall when follow-up lives in personal inboxes, the customer asks a technical question, or a revised proposal is discussed without a recorded approval.

Estimate follow-up keeps contact attempts and customer intent visible while protecting the boundary between coordination and sales, pricing, or system-design judgment.

Scope of work

• Prepare follow up queues
• Record customer responses
• Route technical questions
• Maintain next actions

The exact scope is documented before launch. Work outside that scope is returned or escalated, not guessed.

Inputs and access

• Provide read access to the approved estimate, issue date, validity or expiry note, customer preferences, assigned estimator, financing handoff if applicable, and approved contact sequence.
• Only the current proposal version and company-approved explanation templates should enter the estimate queue; drafts and superseded options stay excluded.

Workflow and deliverables

1. Verify that the estimate is approved, assigned, and within its documented follow-up period before contacting the customer.
2. Review prior estimate contacts so the next message follows the approved cadence and channel preference.
3. Send the approved follow-up, record the customer's words and level of interest without reframing technical or price details.
4. Route requests for revised scope, equipment comparison, discount, financing advice, or technical explanation to the estimate owner.
5. Record the proposal's next action, due date, owner, and source communication.

Deliverables

• An estimate pipeline with current proposal version, last contact, verbatim response summary, next action, due date, and sales owner.
• A review queue separating ready-to-schedule responses from requested revisions, technical questions, price objections, and no-contact estimates.

Quality controls

• Confirm the estimate identifier and approved version before every contact, and never copy price or scope from an earlier proposal.
• Check that each estimate response is tied to its source message and that requested changes remain open until the authorized estimator resolves them.

Decision boundaries

Exception paths

• Pause estimate follow-up when validity has expired, scope appears changed, customer identity is uncertain, or the customer disputes what was proposed.
• Route discount requests, competitor comparisons, financing questions, equipment substitutions, load or sizing questions, and readiness-to-buy responses to the named estimate owner.

Reserved decisions

The support role may coordinate an approved estimate and document interest; it may not alter scope or price, recommend equipment, promise savings, negotiate, or provide technical advice.

Proposal approval, system design, code and permit interpretation, financing guidance, discounts, and final sales commitments remain with qualified authorized staff.

Common starting scenarios

• Start with approved residential estimates issued during one recent week, excluding proposals awaiting technical revision or management approval.
• Another useful start is an aging estimate queue where the estimator first marks the valid version and assigns a specific response path.

Frequently asked questions

Related services