At 8:47 p.m. on a Friday, a homeowner called a roofing company after finding a ceiling stain under a recent storm. No one picked up. By Monday morning, that homeowner had called two more contractors.
This roofing call capture case study follows a 14-person residential roofing contractor that had a steady flow of leads but a leak in the part of the operation that mattered most: answering the phone. Over 60 days, the company turned missed and after-hours calls into 31 booked roof inspections without adding an office employee.
The point is not that every unanswered call becomes a job. It will not. The point is that a roofing prospect with an active leak, storm damage, or a roof replacement question is usually calling because they want to talk now. If your team is on a roof, with a customer, driving, or closed for the day, that opportunity does not wait around politely.
Roofing Call Capture Case Study: The Starting Point
The contractor had four estimators, two office staff, and crews spread across a metro area. Marketing was working. Paid leads, referrals, yard signs, and organic calls were producing roughly 180 inbound calls a month.
But the owner reviewed call records after hearing the same complaint from his office manager: Mondays were chaos. Voicemails had piled up over the weekend. A few callers had hung up and never left a message. Some leads had called during business hours while everyone was tied up.
In the 30 days before the change, 46 inbound calls went unanswered. Of those, 19 left voicemails. The rest simply disappeared.
That does not mean all 46 were good leads. Some were suppliers, job seekers, wrong numbers, or homeowners outside the service area. Still, the owner knew even a small number of lost roofing jobs would cost more than fixing the problem.
The old process was also uneven. A caller who reached the office got help quickly. A caller who reached voicemail might get a callback in 20 minutes, three hours, or the next morning. During hail events and heavy rain, the delay got worse right when demand was highest.
The Fix Was Not More Voicemail
The contractor did not need another inbox for staff to check. It needed someone to answer every call, collect the right information, and book the next step while the homeowner was still engaged.
Within two days, the company had an inbound voice agent in place to handle calls when the office was busy or closed. The setup focused on the questions the team already asked on a good call: Is this residential or commercial? What is the address? Is there an active leak or storm damage? Is the homeowner looking for repair, replacement, or an inspection? Are they within the service area?
The agent was also given clear boundaries. It did not quote roofs, promise insurance coverage, diagnose damage, or pretend to be a salesperson. For urgent active-leak situations, it gathered the details and alerted the on-call person. For qualified inspection requests, it booked an available calendar slot. For questions that required a human, it transferred the call when someone was available or captured a complete message for follow-up.
That distinction matters. Call capture is not about replacing a knowledgeable estimator. It is about making sure an estimator gets a real opportunity instead of a vague voicemail that says, Call me back about my roof.
What happened on a typical call
A homeowner calling after hours would hear a straightforward greeting, not a complicated phone tree. The agent would confirm the reason for the call, check the address against the service area, ask a few qualifying questions, and offer the next available inspection window.
If the caller was a fit and wanted to book, the appointment went directly onto the calendar. If the caller needed immediate help with water coming in, the agent marked the call as urgent and sent the details to the designated person. If the caller was outside the service area or looking for work, the system kept that call from filling an estimator's schedule.
The office staff could see the call notes the next morning. They were not starting from zero. They had the address, roof issue, preferred appointment time, and any urgency flag before they picked up the phone.
Results After 60 Days
Over the next 60 days, the contractor received 371 inbound calls. The voice agent answered 128 calls that would otherwise have gone to voicemail or rung out while staff were occupied.
Of those 128 calls, 54 were legitimate homeowner inquiries. Thirty-one became booked inspections. Eighteen were not a fit because they were outside the service area, were commercial requests the company did not take, or were unrelated calls. The remaining calls were suppliers, recruiting inquiries, and low-intent questions that did not require an estimator.
The 31 booked inspections were the result that changed the owner's view. Before call capture, those calls would have entered the same inconsistent callback queue that had already produced 46 unanswered calls in a single month.
Not every inspection turned into a signed roof. Roofing sales do not work that way. Weather, insurance claims, pricing, and homeowner timing all affect close rate. But the company had created 31 chances to inspect a roof that it may not have had otherwise.
The office manager saw another benefit: fewer Monday-morning fire drills. Instead of sorting through incomplete messages and returning calls in the order voicemail happened to arrive, the team started the day with booked inspections and organized follow-ups.
Why the Numbers Held Up
The result was not caused by a fancy script. It came from speed and consistency.
A homeowner who is calling three roofers after a storm is not comparing your operations manual. They are checking who answers, who sounds competent, and who can give them a clear next step. A fast answer does not win every job, but a missed call makes winning much harder.
The contractor also kept the process narrow. The agent was there to answer, qualify, book, and escalate. It was not asked to handle complicated insurance questions or sell a full roof replacement over the phone. That kept conversations useful and reduced the risk of giving callers bad information.
There is a trade-off here. If your office has enough people to answer nearly every call in real time, and your staff reliably calls back missed leads within minutes, call capture may have a smaller impact. But most roofing businesses have peak periods when that standard breaks down. A storm week, a packed production schedule, or one sick office employee can expose the gap fast.
What Roofing Owners Should Measure
If you want to know whether call capture is paying for itself, do not start with total calls answered. Track the calls that become real sales activity.
Measure missed calls, answered-after-hours calls, qualified homeowner inquiries, booked inspections, show rates, and signed jobs from those inspections. Review the recordings or call notes often enough to catch bad routing, weak questions, or service-area issues. A caller in the wrong ZIP code should not take a valuable inspection slot. A caller with an active leak should not sit in a general callback queue.
It also helps to separate urgent calls from ordinary estimate requests. The right response to water entering a home is different from the right response to someone planning a replacement next spring. Both matter, but they should not be handled the same way.
Relay by Cactus AI runs this as a managed service, which matters for owners who do not want another system to babysit. The phone number, call flow, calendar connection, monitoring, and adjustments need to work every day, not just during the first week of setup.
A roofing company spends real money to make the phone ring. When a caller reaches out after a storm or at the end of a long workday, answering is not a customer-service extra. It is part of the sales process. Start by looking at last month's missed calls. The revenue leak is usually easier to find than owners think.
