AI Receptionist for Roofers

Set the roofing calls the AI receptionist is authorized to handle

The AI receptionist is authorized per account to greet callers, ask roofing intake questions, and route the conversation toward a live transfer, a callback request, or a structured lead — and nothing outside that scope. It does not operate as a general business assistant; its authorized behavior is scoped to the roofing company's own services, ZIPs and account settings.

Two configuration choices define the baseline for every call. First, whether the account runs ring-first (the roofer's verified forwarding number rings for an agreed number of seconds before the AI picks up) or AI-first (the AI answers immediately on every call during business hours). Second, a separate after-hours mode governs behavior outside the configured business-hours schedule, which is itself set in the account's business timezone — a 6 p.m. call in a Texas market and a 6 p.m. call in a Pennsylvania market are evaluated against each account's own local schedule, not a single shared clock.

• Ring-first or AI-first is a per-account setting, decided when the account is configured, not a dynamic choice made per call.
• Business-hours schedule is set in the account's own business timezone.
• After-hours mode is configured separately from business hours and can itself be ring-first, AI-first, or voicemail.
• If the AI's allotted minutes for the period run out, the call falls back to ringing the forwarding number or to voicemail.
• Ringing only works where a verified forwarding number is on file; without one, that fallback isn't available.

What authorization does not extend to

Authorization to take a call does not mean authorization to answer every question on it. The receptionist is scoped to greeting, intake, and routing — it is not configured to perform diagnosis, quote pricing, or make commitments about scheduling, insurance, or licensing, regardless of how confidently a caller frames the question.

Ask useful intake questions without inventing project answers

The receptionist asks roofing intake questions — what's happening, where, and how urgent it is — and saves each fact to the lead record as it learns it, rather than waiting until the end of the call to summarize. It does not answer project questions it isn't equipped to answer; where a caller asks something outside its approved scope, it says so rather than guessing.

A typical intake exchange covers the caller's name and contact number, the property address or ZIP, what they're observing (a stain, an active leak, visible storm damage, a planned project), and how urgent the situation sounds based on what the caller describes. One capability worth naming specifically: the receptionist can text the caller a link to submit a photo, and that capability is limited to ground-level and inside-the-home photos — it does not ask anyone to get on a roof to take a picture.

1. Capture the caller's name, callback number and property address or ZIP as the conversation progresses.
2. Ask what the caller is observing, in their own words, and save that description rather than paraphrasing it into a diagnosis.
3. Offer a text link for a ground-level or inside photo where that would help the intake.
4. Note the service the caller is asking about, matched against what the account's approved knowledge actually covers.
5. Never state a price, a timeline guarantee, an insurance outcome, or a roof-safety conclusion during intake.

Why facts are saved as they're learned, not reconstructed afterward

Saving each fact to the lead record as the AI learns it, rather than generating a single end-of-call summary, means a dropped call or an early hang-up still leaves a usable partial record for your team instead of nothing at all. It also means the recorded detail reflects what the caller actually said, not an inference made after the fact.

Use service-area and availability information from the approved account

The receptionist only references services, ZIPs, hours and knowledge that have actually been approved and loaded into the account configuration — it does not invent a service the company doesn't offer or confirm availability it has no data to support.

That means if a caller asks about a service outside what the account lists, or a ZIP outside the territory the account covers, the AI doesn't guess at whether the company could still help; it captures the request honestly and leaves that judgment to your team. The same applies to scheduling language: the receptionist records a callback or appointment request — noting what the caller is asking for and when they'd prefer it — without promising that a specific slot exists, since it has no visibility into your crew's actual calendar.

• Services referenced on a call come only from the account's approved service list, not a general assumption about what roofers typically do.
• ZIP and territory matching uses the same account configuration used elsewhere in the lead pipeline.
• Business-hours and after-hours behavior reflect the schedule set for that specific account and timezone.
• A callback or appointment request is recorded as a request, never confirmed as a booked slot.

An illustrative example, using your own assumptions

Say a roofing company configures its account as ring-first during business hours with an 18-second ring window, AI-first after hours, and a after-hours fallback to voicemail once AI minutes for the month are used up. A caller phoning at 9 p.m. would reach the AI directly under the after-hours setting; if that account's monthly AI minutes were already exhausted, the same call would instead route to voicemail. This is a labeled example built from settings a company could choose — it describes how the configuration options combine, not a promise about what any specific account currently has configured.

Transfer urgent or unsupported enquiries through a tested fallback

The receptionist is built to recognize a defined set of urgent conditions — water actively pouring in, a tree down on the roof, a visibly sagging structure, or water near electrical components — and to attempt a live transfer to a person as soon as one of those is described.

If the live transfer succeeds, the call continues with a person on the line and the urgency flag stays attached to the lead record. If the transfer attempt fails — nobody picks up on the receiving end — the AI tells the caller directly that the transfer didn't connect, rather than pretending it did, and triggers an alert to the team so a human can follow up immediately rather than relying on the caller to call back.

1. Recognize the described urgent condition from what the caller actually says, against the approved list of urgent triggers.
2. Attempt a live transfer to the configured escalation contact.
3. If the caller describes active danger, tell them to move away from the hazard and call 911, independent of whether the transfer connects.
4. If the transfer fails, state that clearly to the caller and alert the team so the gap doesn't go unnoticed.
5. Record the urgency flag and the transfer outcome on the lead so your team sees exactly what happened on the call.

Danger guidance is not a substitute for a dispatch promise

Telling a caller to move away from a hazard and call 911 when there's active danger is a safety instruction, not a claim that the roofing company itself is dispatching an emergency crew. The receptionist doesn't promise emergency dispatch timing or confirm that a specific crew is en route — that commitment, if your company makes it, comes from your team after the transfer or callback.

Send the conversation and structured lead to the roofer

Once a call ends, the structured lead — the facts captured during the conversation, the urgency flag if one applied, and the transfer outcome — is delivered through the same pipeline used for other network leads, into the CRM connection your account already has set up.

Where recording is enabled for the account and permitted under applicable consent rules, the recording and a transcript are attached to the lead record alongside the structured fields. Recording-consent mode is supported as part of the account configuration, and it's set up to reflect the rules that apply to where the call is coming from, rather than a single default applied everywhere.

• Structured fields (contact info, address or ZIP, described issue, urgency flag, transfer outcome) are delivered with the same reliability pipeline as other network leads: queued, sent, delivered or failed, with retries and a fallback alert.
• Recordings and transcripts are attached where recording is enabled and permitted, not by default on every account.
• A callback or appointment request appears on the lead as a request, labeled as such, not as a confirmed booking.
• Your team can review the call record and take over the conversation thread from wherever the AI left off.

What the delivered record does not claim

The delivered lead reflects exactly what was captured and what happened on the call — it doesn't backfill a diagnosis, a price estimate, or a confirmed appointment that the AI wasn't authorized to provide during the conversation itself. If a field wasn't captured, the record shows it as missing rather than filling it with a guess.

Review call quality, access and ongoing configuration

Call quality and configuration on an active account are reviewable on an ongoing basis — your team can listen to or read recorded calls where enabled, check whether urgent calls were correctly flagged and transferred, and adjust the approved service list, ZIPs, schedule or escalation contacts as your business changes.

This review step exists because an AI receptionist's usefulness depends entirely on whether its configuration still matches reality: a forwarding number that changes without being updated breaks the ring-first fallback, a new service your company starts offering won't be referenced on calls until it's added to the approved knowledge, and an escalation contact who's left the company needs to be swapped before the next urgent call comes in.

1. Confirm the verified forwarding number on file is still correct, since ring-first and voicemail fallback both depend on it.
2. Check that the approved service list and ZIP coverage match what your company currently offers and serves.
3. Review the business-hours schedule and after-hours mode against your actual operating hours.
4. Confirm escalation contacts for live transfer are current.
5. Spot-check recent calls, where recording is enabled, to confirm urgency detection and transfer behavior are working as configured.

Availability is reviewed per market, not guaranteed

Whether the AI receptionist program is available for your account, and what configuration options apply in your specific market, is confirmed during a Roofing Market Review rather than assumed from this page. Inventory and feature availability are reviewed per market and are never guaranteed nationally.