When the storm hits, the phone does too
After a hailstorm or a band of high wind moves through a service area, a roofing company can go from a quiet evening to dozens of calls in an hour. Homeowners with water coming through a ceiling do not wait politely until 8 a.m. They call, and if no one answers, they call the next number on the list.
This is the problem a roofing answering service is supposed to solve. Not magic, not a robot that climbs your ladder, just a reliable way to answer the phone when your crews are on rooftops or asleep, and to hand you clean intake notes you can act on in the morning or on call.
I work with OnCrew, so treat this as a vendor-biased guide. Abe, the founder of OnCrew, built the product around one stubborn belief: an answering service should capture and organize information honestly, and leave the real decisions to the contractor. With that bias stated up front, here are the intake rules I would use to evaluate any after-hours option for storm-call surges, whether you pick us or not.
What a roofing answering service should and should not claim
Let me be blunt about scope, because a lot of marketing in this category is not. A roofing answering service answers or receives your forwarded calls, captures the caller details, classifies the type and urgency of the request, summarizes the conversation, alerts or notifies your team, and preserves the context so a callback is easy. That is the honest list.
What it should not claim to do is send a truck, promise an arrival time, set an appointment, or decide whether a situation is a true emergency. Those are your calls. A service that makes promises it has no authority to keep, like telling a homeowner a truck is coming, sets you up for an angry customer and a damaged reputation. Good intake sounds like, "I am taking your details now and getting them to the on-call team right away," not a promise the service cannot keep.
Intake fields that actually matter
The value of a roofing answering service lives in the fields it captures. After a storm, you want a consistent record, not a scribbled name and number. At minimum, the intake should capture:
- Full name and the best callback number, read back to confirm.
- Service address, including gate codes or access notes if the caller offers them.
- Caller role (more on this below).
- Property type and a rough roof description.
- A plain description of the problem in the caller's words.
- Whether water is actively entering the home right now.
- How the caller found you, which is gold for tracking storm marketing.
Consistency is the point. When ten calls land in twenty minutes, a uniform intake template lets you triage the stack quickly instead of decoding ten different notes.
Active leak and storm-damage triage
This is where honesty matters most. A roofing answering service can ask the questions that help you sort urgency, and it can flag a call as urgent based on the answers, but it should not pretend to make the emergency judgment for you.
Useful triage questions during intake include: Is water coming in right now, or is this damage you noticed after the weather passed? Is the ceiling sagging, or are electrical fixtures involved? Is anyone unsafe in the home? The service captures those answers, classifies the call as high urgency, and alerts your on-call contact so a human can decide what happens next. The decision about whether to roll out at 2 a.m. stays with you.
For the homeowner, the intake can offer general, non-technical reminders that any operator can give, like moving belongings out from under a drip and putting down a bucket. It should not give roofing instructions, climbing advice, or insurance direction.
Caller role changes everything
A storm call from the homeowner is different from a call from a tenant, a property manager, or an adjuster. Capturing the caller role early shapes the whole record. A tenant may not be able to authorize work or share the full address history. A property manager may handle ten buildings and need a reference number. An adjuster is chasing documentation, not a repair. A roofing answering service that records the role up front saves you a frustrating second call to figure out who you are even talking to.
Property type and access details
Residential, multifamily, and commercial roofs lead to very different conversations. A steep asphalt roof on a two-story house, a flat membrane on a strip mall, and a metal roof on a barn all carry different access, safety, and timing realities. The intake should capture property type and any access notes the caller volunteers, so the person calling back has a picture in mind before they dial. The contractor still owns every site-safety and roof-access decision; the service is just writing down what the caller said.
Photo and document handoff
Storm damage is visual. A strong roofing answering service makes it easy for a caller to send photos or documents and ties that media to the intake record, so when you open the call summary you can see the ceiling stain or the pile of granules in the gutter. Ask any vendor how photo handoff works, where the files live, and how they stay attached to the right call. Loose photos with no matching record are nearly useless during a surge.
Owner and on-call alerts
Capturing a great record means nothing if it sits in a queue. The point of after-hours intake is the alert. A roofing answering service should notify the owner or the on-call person quickly, with enough of the summary in the alert that the human can judge urgency before opening anything. Ask how alerts are delivered, whether you can route urgent flags to a different person than routine messages, and how escalation works if the first contact does not respond.
Transcript and summary retention
A week after a big storm, you will want to look back. Retention of transcripts and summaries lets you reconcile which calls turned into work, settle disputes about what a caller said, and measure how a storm event actually performed. Ask each vendor how long transcripts and summaries are kept, who can access them, and whether you can export them into your own records. A roofing answering service that captures plenty but throws it away in a day is leaving value on the table.
The callback window
Speed wins storm work. Decide on a callback window your team can actually honor, for example a human callback within a set number of minutes for urgent flags and by the next morning for routine ones, and make sure your intake setup supports it. The service does not perform the callback for you; it preserves the context so your callback is fast and informed. Set the window, then hold yourself to it.
Questions to ask any vendor
Before you sign with anyone, including us, ask:
- What exactly do you do, in plain verbs, and what do you explicitly not do?
- How do you handle an active-leak call without promising a truck?
- What fields are captured, and can I customize the intake script?
- How are photos and documents attached to a call?
- How fast and how reliably are owner and on-call alerts delivered?
- How long are transcripts and summaries retained, and can I export them?
- What does a true call surge cost me?
That last question matters because storm volume is spiky. Read the pricing for the spike, not the quiet week.
Where OnCrew fits, plainly
OnCrew answers or receives your forwarded calls, captures and classifies the request, summarizes it, alerts your team, and preserves the callback context. OnCrew is $49/month for 100 calls, then $0.99 per extra call. The contractor owns pricing, scheduling, dispatch, ETA, appointments, CRM setup, site safety, roof access, insurance guidance, emergency judgment, and field decisions.
That division of labor is the whole philosophy Abe built into the product. The roofing answering service handles the phone and the paperwork of intake. You handle the roof.
If you want to see the roofing-specific setup, start here:
https://oncrew.ai/answering/roofers
For a deeper guide and intake templates:
https://oncrew.ai/resources/roofing-answering-service
And the plan details are here:
Pick the vendor that tells you the truth about what happens when the storm calls start. A roofing answering service earns its keep by capturing clean information and getting it to a human fast, not by making promises it cannot keep.
