Keep the first call focused

A homeowner does not need to complete a long questionnaire to explain why they called. Start with the request, then collect enough information for the person who will handle it. If the caller already gave a detail, acknowledge it instead of asking again.

  • Name and preferred callback number, read back for accuracy.
  • Property address, including city, state, and ZIP code.
  • Reason for calling, recorded in the homeowner's own words.
  • Whether this is a new inquiry or an existing project.
  • Preferred language and contact method.
  • Availability for a callback or visit, when relevant.
  • Assigned owner and agreed next action.

Use optional fields for details that do not affect the next step. For example, an email address is useful when the homeowner wants information by email; it should not distract from getting the property location and callback number right.

Use this opening and intake script

Replace the bracketed wording with your approved business details. This is a sample conversation, not a description of a live LeanLine call.

Thank you for calling [company name]. This is [name]. How can I help with your roof today?

I can take those details for [contractor or team]. May I have your name and the best number to reach you?

What is the address of the property?

Thank you. You are looking for help with [brief summary]. Is that right?

Have you worked with our team on this property before?

Would you prefer the next update by [approved contact options]? And is there a good time to reach you?

Leave space for the caller to answer. The script is a guide to listening, not a reason to interrupt. If someone is unsure of the roof material or age, record that uncertainty instead of guessing. The contractor can clarify details during the appropriate review.

Prepare for questions the answering team cannot resolve

Decide these boundaries before calls start. Your team needs a sentence it can use when a homeowner asks for a price, an immediate visit, or a technical conclusion that the representative is not authorized to provide.

For pricing: I can pass the details to [person]. They will need to review the scope before confirming a price.

For an unavailable appointment: I do not have an approved opening at that time. I can send your preferred time to [person] for review.

For a technical question: I want the right person to answer that. I will include your question in the notes for [person].

For urgent calls, follow the contractor's written escalation instructions. Do not improvise repair advice or promise a response time that has not been approved. Record what the caller reports without diagnosing the condition of the property.

Write notes the next person can act on

Use a consistent note format so the roofer does not have to reconstruct the conversation. Here is a fictional example using placeholders rather than customer data.

New estimate request. [Homeowner] at [property address] is considering a roof replacement. Best callback: [verified number]. Prefers English and a phone call in the afternoon. Requested a visit next week; no appointment confirmed. Assigned to [owner] to review availability. Caller was told that [owner] would review the request; no price or response time promised.

Keep the original request separate from your interpretation. “Caller noticed a stain on the ceiling” records what was said. “Roof needs replacing” adds a conclusion the caller or representative may not be qualified to make.

Close with one clear next step

Before ending, read back the important details and explain exactly what has been agreed. If there is only a callback request, call it a callback request. If there is a confirmed appointment, repeat the day, time window, address, and any approved access instructions.

I have [summary] for the property at [address]. The next step is [approved action] with [person or team]. We will use [agreed contact method]. Is there anything important I missed?

Do not turn a scheduling request into a sales promise. A complete intake helps the team prepare; it does not guarantee an estimate, a signed proposal, or a particular outcome.

Check the script against actual calls

After using the script, review where callers hesitate and where the roofer still needs to ask the same questions again. Shorten questions that produce duplicate information. Add a field only when it helps someone make the next decision.

Have a named owner maintain the approved version, including service areas, available contact methods, and escalation instructions. Give the answering team a way to flag unclear cases. A short script with clear boundaries is easier to keep accurate than a long script full of promises no one can verify.