Track every open roofing estimate with one responsible person, its current stage and a dated next action. Record the customer’s latest response alongside it. A reply, postponement, decline or request to stop must change the next action before another follow-up happens.
This is a proposed review routine for residential retail estimates. It connects demand, the conversations already started, with fulfillment, where an accepted estimate needs a clear handoff to the people doing the work. Insurance restoration and commercial bidding need their own processes.
Make the list answer one question
When you open the list, you should be able to answer: “Who needs to do what next?” Start in your existing CRM. If you do not have a suitable system, a small shared tracker can support this review. Choose one authoritative record and keep any review view linked to it, so people do not maintain conflicting copies.
| Field | Useful entry |
|---|---|
| Estimate reference and owner | A reference to the original estimate and one person responsible for the next action, with absence cover. |
| Stage | For example: being prepared, sent, question to answer, postponed, accepted, declined or closed. Define these in your own process. |
| Latest response | What the customer actually said and when. Separate an unanswered message from a clear decision. |
| Next action and date | A specific action such as “answer the scope question” or “check on the date the customer requested.” |
| Contact status | Agreed channel and contact preferences, any restrictions or stop request, and the record your business uses to verify permitted contact. |
| Pause, stop or handoff | Whether follow-up is paused or stopped and why; for accepted work, who receives and acknowledges the handoff. |
These are suggested operating fields, not a claim that a particular product provides every column or enforces each rule. An owner working alone may handle every step. A staffed team needs explicit ownership when sales and production are different people.
Let the response change the work
Synthetic example, not a customer result: Estimate R-018 has been sent. The next review finds a customer question about what the estimate includes. The responsible person changes its stage to “question to answer” and assigns the answer. Repeating a generic “just checking in” message would leave the real question untouched.
The customer later asks to revisit the decision on a particular date. The responsible person records that date and pauses other follow-through. If the customer subsequently declines or asks for no further contact, the responsible person stops that follow-through and records the decision.
If an estimate is accepted, the sales step needs a receiving person: who checks the agreed scope, what remains unresolved, and who takes responsibility for the next scheduling decision? An “accepted” label alone does not demonstrate that production has received the job.
Two short templates for a person to adapt
Use these only where the intended contact is permitted. Check the current record first and tailor the words to the actual conversation. Manual sending still needs the applicable permissions; this guide does not determine whether any particular message or channel is lawful.
Check receipt
“Hello [name], I’m checking whether you received estimate [reference] from [business]. Is there a question about the proposed scope that you would like us to answer? If another time or no further follow-up would suit you, please let us know.”
Return with the promised answer
“Hello [name], you asked about [specific question] in estimate [reference]. Here is the answer checked by [responsible person]: [answer]. Does that address the question, or is there something we should clarify?”
These are editorial examples. They do not create consent, a required cadence or a promise about availability, price or results. Never invent urgency or imply the customer has approved work they have not approved.
Check the CRM before adding automation
Product check, 1 November 2026: JobNimbus’s official time-based automation guide describes conditions, assigned tasks and an Engage text-message action. Some triggering records depend on enabled features. The page has no revision date, so verify the current account. It does not establish automatic reply, decline or opt-out stops, including for text actions.
If you automate anything in this routine, limit it to internal reminders or assigned tasks; customer contact stays human-reviewed and subject to the applicable permissions. This guide does not cover automatically sending customer messages. Test queued tasks after a reply, postponement, acceptance, decline or stop request, and a stage change just before a task is due. If a stop path is unverified, keep the process under manual review.
How often should we follow up?
There is no universal interval in this guide. Base the next action on the actual conversation, the customer’s preference and your permitted contact process. A review date can be an internal check rather than another customer message.
Start with the open estimates you already have
Review a small set in the current system. Assign a person and a useful next action, then resolve any conflicting record. See roofing and trade office workflows for the wider handoff. If one repeated gap remains, Abundance Applied can be a starting point for discussing it without assuming you need a second CRM.
Sources
Product documentation checked 1 November 2026. Features depend on the current plan, permissions and setup.