How do you open the appointment?
Thanks for meeting with me. What prompted you to call, and what would you like us to understand before we look at the roof? Confirm access and purpose first.
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.
Confirm which problem the homeowner wants addressed before moving into the inspection. A leak concern and a planned replacement discussion may lead to different priorities. Check access and permission using your company’s actual process. The opening should reduce assumptions and help the homeowner understand the visit. It is not a place for manufactured urgency or a rehearsed claim about inevitable damage.
Which discovery questions help?
Ask what the homeowner noticed, how long it has been happening and what matters most in resolving it. Listen before offering a scope.
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.
Ask open questions and record the answers accurately. The homeowner may have concerns about disruption, timing or materials rather than a simple price target. Do not turn their words into a diagnosis. A useful discovery note preserves what they observed and what matters to them. It should help the next person understand the conversation without adding an interpretation the customer did not provide.
How do you explain the inspection?
Describe what you will examine and what you cannot confirm yet. Ask permission for access and use your actual company inspection process.
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.
Explain the parts of the assessment you can complete and the limits of access or conditions. If a finding requires further review, say so. Reps should know which technical questions belong with qualified staff. The inspection process should not create a confident conclusion simply because the customer expects one. Clear limits make the later scope discussion more responsible and easier to document.
How do you show observations?
Use relevant photos and notes. Separate visible conditions from suspected causes; do not present a photo as proof of insurance coverage.
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.
Use captions or spoken explanations that distinguish the visible condition from a suspected cause. Ask whether the customer understands the observation before moving to options. Avoid treating a photo as proof of insurance eligibility or a universal need for replacement. Keep the supporting material with the proposal record so the follow-up conversation uses the same evidence rather than a new version of the story.
Start with your current website.
A free review of your site, Google presence and lead follow-up.
How do you present options?
Explain valid scopes with inclusions, exclusions and questions still requiring confirmation. Avoid a forced choice that hides a reasonable repair option.
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.
If repair and replacement are both valid options, describe the actual differences and limitations. Do not present a forced choice whose purpose is only to push the larger scope. The written proposal should identify what is included, what is excluded and any assumptions still needing confirmation. A homeowner should be able to compare the options after the visit without remembering every sentence of the presentation.
How do you discuss price?
Connect the price to the written scope, materials and responsibilities. Ask what needs clarification instead of assuming every hesitation is a price objection.
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.
Link the price to the approved scope and ask what is unclear. A question about materials needs a different answer from a question about payment timing. Avoid pressure tactics or unsupported criticism of another roofer. If the scope changes, record the revision. The follow-up should refer to the current proposal, not an amount mentioned before the inspection or before required information was available.
How do you handle insurance questions?
Explain the contractor’s role accurately. Coverage and claim decisions belong to the insurer; never promise approval or represent uncertain findings as final.
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.
The insurer decides coverage and claims according to its process. The contractor can explain observations and the role it actually performs. Do not promise approval, payment or a result the company does not control. A rep who is unsure should escalate the question rather than improvise. The playbook should preserve that boundary so consistent language does not become a consistent unsupported claim.
How do you close without pressure?
What questions should we answer before you decide? Agree on a written estimate or next conversation, and record the customer’s preference.
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.
End with the next action the customer actually agreed to. They may want the written estimate, another question answered or time to consider the options. Record the preferred contact method and decision timing. A follow-up message should fit that agreement and stop when the customer declines. The goal is a clear conversation and handoff, not a promise that every inspection will become a signed job.
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