Roofing leads arrive in a wave after a storm, and they cool fast. A homeowner with water coming through the ceiling will not leave a message and wait. They will call the next roofer. Your response in that first stretch is most of the game.
Picture a fictional morning after rough weather. One person reports water indoors. Another found shingles in the yard. A property manager wants several buildings reviewed. An existing customer asks whether their booked job is changing. Putting all four in “storm leads” gives the spreadsheet a category. It does not give anyone a plan.
Build an honest inspection queue before sending more reminders. A customer needs to know whether an inspection is requested, confirmed or completed. Each state should lead to different words and a different staff task.
The Quiet Protocol's AI Receptionist starts at US$449 per month with free setup (normally US$1,495), with no contract and call minutes included. We configure and test the approved questions and handoffs, then monitor the installed route. When the office also needs a defined inspection or estimate-follow-up process, we agree that additional scope with you. The purchase should move requests into useful records and human-owned decisions, rather than let automation promise a crew you do not have.
Keep the first record small and accurate
Collect the callback route, property address, caller's role, property type and their description of what they noticed. Record whether they say water is entering now and any concern needing the company's approved human escalation path. Do not turn “possible hail damage” into a confirmed roof assessment.
A property manager's multi-building request needs different scheduling review from a single address. A tenant may be reporting the issue while a different person must authorize access or work. Capture that relationship without assuming the caller has agreed a contract on the owner's behalf.
Ask only for information the caller already has. The intake path should not direct anyone onto a roof or make collecting photos a condition of getting a human response. The qualified roofing team decides what it can assess and when. This guide supplies a receiving process, not inspection or property-safety instructions.
One request, one visible next action
- Property and contact
- Address, caller's role, callback preference and person needed for access or authorization.
- Known and uncertain
- Reported condition in the caller's words. Preserve anything not yet inspected as unverified.
- Inspection state
- Requested, awaiting capacity review, confirmed, completed or declined. A request is never labelled a booked visit.
- Company action due
- Named colleague, action owed, next review point and the exact customer promise.
- Following the visit
- Scope being prepared, estimate delivered, customer question open or work scheduling under review. Cancel reminders that no longer fit.
Offer a review point you can keep
If dispatch must review the request, say that. Proposed wording is: “We have your inspection request. Our office will check whether we can offer a visit at that address and contact you with the next step.” Add the genuine review point only when the assigned team can keep it.
If no suitable capacity exists, tell the customer directly. An inspection request is not an appointment, and a waitlist is useful only when a person owns it. Do not make a homeowner infer that nobody is coming from the absence of a second email.
The capacity review should account for area, travel, appointment type, crew and the company's own access and inspection requirements. A property manager requesting several buildings should not receive a single-home slot because it is the first blank square in the calendar.
When capacity changes, update both the queue and the promise. A cancelled crew day must stop new confirmations and surface existing commitments for a person to handle. The customer and dispatcher should see the same appointment state.
Follow up to complete the next job
Before inspection, follow up to confirm access, explain a real change or keep the agreed contact date. After inspection, deliver the promised scope or assign the person preparing it. If the homeowner asks a question, pause generic nudges and give that question to someone who can answer.
A simple illustrative update is: “Our inspection is complete. [Named role] is preparing the written scope. We will contact you at [agreed review point]. If you have a question in the meantime, reply here and the office will route it.” Use that only when the record supports every part.
If the customer asked to reconnect after another appointment or discussion, create the dated task. Do not fill the waiting period with reminders. Once the quote is current and delivered, use the estimate follow-up guide for the email and stop-rule decision.
Separate inspection notes, your proposed work and the insurer's decision. NAIC's guidance explains that roof-loss payment depends on policy and coverage details, including deductibles and depreciation treatment. A receptionist should not promise approval, coverage or a replacement funded by insurance. NAIC roof-loss guidance
Check the office's work before expanding the send
Arrange labelled test requests for an ordinary homeowner, a multi-building inquiry, an existing customer and an address outside coverage. Fill the relevant inspection capacity and try again. Inspect the receiving record and listen to the precise promise.
Then reply with a question, a changed time and a decline. Check that irrelevant reminders stop and a person receives any new action. A reply must change the workflow, rather than join a separate inbox the dispatcher never sees.
In the TQP implementation, these are defined acceptance checks for the agreed route. Our continuing work monitors the installed paths and exceptions. Your office and qualified field team remain responsible for the service decisions and inspection capacity.
Review requests awaiting company action separately from customers considering estimates. A queue with many emails sent can still contain unanswered questions. Count confirmed visits and completed inspections separately; neither is a guarantee of a signed or completed roofing job.
Bring your actual inspection states and one anonymized caller thread to our home and field services team. Let us make the next action clear enough for the office to carry. After a storm, a useful update earns more trust than another automated “still interested?”
Frequently asked questions
How should a roofing company follow up after a storm inquiry?
Start with a usable request record and the review point the company can keep. Follow up to complete a specific next job, such as missing location details or inspection scheduling, rather than sending repeated generic sales messages.
Should the website promise an immediate storm inspection?
Promise only the review or appointment the operation can provide. Capacity and service fit still need checking. A request received is different from an inspection confirmed.
What can TQP connect for a roofing company?
We can join the website inquiry, approved intake, receiving team and follow-up path. The system preserves the customer's request and the next action, so a busy storm period does not leave you remembering every inquiry yourself.
We configure the agreed caller questions, contact records and handoffs, then test and maintain the installed receptionist. For inspection and estimate follow-up, we agree the additional process scope around your actual staff and crew capacity.
Build a roofing inquiry queue your office can carry