What should you agree before following up?
Ask the customer how they prefer to be contacted and when they expect to decide. Record that preference alongside the estimate.
Begin with the customer’s actual task. Write down the question they are trying to answer and the information your office needs to respond. Review one recent inquiry with the person who handled it. Where did the conversation stall? Which detail was missing? Turn that observation into a clear step rather than adding another vague promise. The aim is a process that your team understands and can repeat. Different services may need different questions, so do not force every request into the same script.
In remodeling, a customer may need to compare revisions, discuss a budget or coordinate timing with the household. Ask about that decision before choosing a follow-up schedule. A quick repair quote may not need the same sequence. Record the preference and the reason for the next contact. The conversation should guide the cadence rather than a universal day-two, day-five formula.
What should the first message say?
Hi [Name], I’m checking that you received the estimate for [project]. What questions can I answer? Reply here if you would like to discuss next steps.
Put the decision into a short checklist that staff can use while working. Include who owns the next step and what happens when information is missing. The checklist should reflect current capacity and actual company policies. If a detail changes, update the website, messages and internal notes together. This prevents a customer receiving one explanation online and a different one from the office. Keep the wording plain enough that a new employee can understand it without interpreting marketing language.
The example message checks receipt and invites questions without assuming the customer is ready to accept. Keep the project reference brief and appropriate to the channel. Do not expose a detailed address or financial information in a text unnecessarily. Use a reply destination the office actually monitors. A message that asks for questions must create a task when the customer answers.
How do you find the real concern?
Ask whether the customer needs clarity on scope, timing or another issue. Do not assume price is the only reason a decision takes time.
Use a realistic example during review, but do not publish invented customer evidence as proof. A sample helps test the process; a real testimonial requires permission and an actual experience. Check whether the information is appropriate for the channel. Public content should never expose a customer’s address, private finances or household details. A message that looks professional is still a problem if it reaches the wrong person or reveals more than the conversation needs.
Listen to what remains unresolved. A customer may be uncertain about scope, disruption or the distinction between options. Answering with a discount before understanding the question can create confusion. Explain the relevant part of the current proposal and identify any revision required. The record should preserve the new question so another team member does not restart the same generic pitch.
How do you explain competing quotes?
Compare inclusions, exclusions, preparation and responsibilities. Avoid criticizing a contractor whose proposal you have not reviewed.
Check the handoff, not just the first visible screen. A customer should know what happens next and a team member should see the required action. Test the phone link, form or reply path on a mobile device. Follow the request through the tools your team actually uses. If one person must copy details manually, name that responsibility rather than pretending the system is fully connected. A dependable small workflow is more useful than a large setup with unclear ownership.
If the customer mentions another proposal, ask which differences they want to understand. Review comparable work, exclusions and responsibilities rather than disparaging an unseen competitor. A lower number may describe a different scope. Keep the discussion factual and acknowledge uncertainty. The buyer should be able to compare the documents after the conversation without depending on a sales rep’s unsupported interpretation.
Start with your current website.
A free review of your site, Google presence and lead follow-up.
How often should you follow up?
Use a bounded cadence agreed by your business and respect a decline or opt-out. There is no universal schedule that guarantees a sale.
Review the scope with your team before turning a suggestion into a public claim. Availability, qualifications and pricing should match what the company can deliver. Avoid a guarantee when outcomes depend on the customer, market or site conditions. If a technical or policy detail is uncertain, verify it with the relevant provider or qualified person. Keep a record of the answer so future edits do not revive an old assumption. Accuracy matters more than a confident-sounding sentence.
A bounded sequence should reflect the company’s actual policy and the customer’s preferences. Stop when they decline or opt out. Do not keep an inactive estimate in a nurture sequence simply because an automation is available. Repeated contact can become pressure when it no longer fits the decision. A professional process includes a clear way to end the conversation.
When should a person take over?
A customer asking about revisions, finance or a complaint needs a real reply. Pause generic messages so they do not contradict the conversation.
Use your own records to decide whether the change is useful. Look for missed handoffs, repeated questions and contradictory messages. Do not assign a revenue lift to a new process without dependable evidence. A review should distinguish what you observed from why you think it happened. Keep the first change narrow enough to understand, then refine it when the team sees how customers respond. This makes maintenance practical instead of turning every adjustment into a complete rebuild.
A scope revision, finance question or complaint is not a reason to send another generic reminder. Assign it to a person and pause messages that may contradict the reply. If several team members are involved, identify one owner for the next action. The customer should not need to reconcile two different answers from the same company because the status record was incomplete.
What should the CRM record?
Keep the scope version, customer questions, owner and next action. A status label is only useful when someone knows what it means.
When software is involved, define the source of truth for each piece of information. The website may collect a request, the CRM may own follow-up and another tool may own the job. A status update should not trigger the same message twice. Test cancellations, changed dates and a customer who already replied. The exception path deserves the same attention as the normal path. Your team needs a way to stop or correct a workflow without losing the underlying customer record.
Record the current proposal version, question, contact preference and next action. Won, lost and inactive should have meanings the team understands. Do not mark an estimate accepted because a customer opened a message. The record should describe an actual decision or task. This makes the follow-up review useful to the office and prevents optimistic statuses from hiding unfinished work.
How do you close an inactive estimate?
Send a short final note if appropriate, then mark the opportunity inactive according to your company process. Do not imply pricing or capacity stays open forever.
Choose the next action before ending the conversation. It may be a call, a site visit, a written proposal or a request for more information. The right step depends on the service and what is already known. Tell the customer only what has actually been agreed, and keep internal notes factual. If they decline, respect that decision. A clear ending helps your office prioritize active work and avoids continuing messages that no longer fit the customer’s situation.
A final note can say that the company will leave the decision with the customer and remain available for questions. Do not promise that an old price or start date remains valid indefinitely. If the customer returns later, review the scope and capacity again. A clear ending is part of good customer service and helps staff focus on active opportunities without erasing useful history.
ABOUT THE AUTHOR
George · Vercano Partners
George co-runs GRIPGO Roofing and has more than three years of experience building sales scripts and processes.
Meet George