I'm Abe, founder of OnCrew, so read this with the bias up front: I build an AI answering service for contractors, and roofing is one of the trades that pushes it hardest. When a hailstorm rolls through at 9 p.m., a roofing company's phone does not ring once. It rings dozens of times in an hour, and most of those callers will hire whoever picks up and sounds organized.
This article is about the intake rules that keep that surge from turning into chaos: what to capture, how to classify urgency, and where the line sits between an answering service and your actual field operation.
What a roofing answering service does, and what it does not
Be precise here, because the wrong mental model leads to bad expectations.
An answering service like OnCrew:
- Answers or receives calls you forward to it, day or night.
- Captures caller details: name, callback number, property address, and the reason they called.
- Classifies and summarizes urgency, so a 2 a.m. active leak reads differently from "call me about a quote next week."
- Alerts and notifies your team through the channels you choose.
- Preserves callback context, so whoever follows up is not starting from zero.
What it does not do is run your business. OnCrew does not set your pricing, book confirmed appointments on your behalf, decide dispatch order, quote an ETA, or make any field decision. It does not send roofers anywhere. It does not give insurance guidance or tell a caller what their policy covers. Those calls are yours.
Here is the clean split:
- OnCrew handles: answering, intake, urgency classification, summaries, alerts, and callback context.
- You own: pricing, scheduling, dispatch, ETA, site safety, roof and ladder access, insurance guidance, appointments, CRM setup, and every field decision.
If a vendor blurs that line and implies the service itself will commit your crew to a timeline, walk away. An answering service captures and routes. Your team decides and acts.
A roofing answering-service evaluation checklist
Use this when you compare options:
- Does it answer forwarded calls around the clock, or only during set hours?
- Can it capture structured intake (name, number, address, issue) instead of a vague message?
- Does it classify urgency, or does every message land in one undifferentiated pile?
- Can you control how and where alerts arrive (text, email, your routing)?
- Does it preserve the full callback context so your follow-up is informed?
- Does it stay in its lane, leaving pricing, scheduling, and dispatch to you?
- Is the pricing transparent and usage-based, with no mystery per-seat tiers?
- Can it handle a sudden volume spike with clear fallback rules for any overflow?
- Does it avoid telling callers anything you have not authorized?
A storm night will expose the tool that fails the last two.
Four after-hours call scenarios
Scenario one: active interior leak during a storm. It is 11:40 p.m., water coming through a bedroom ceiling. Intake captures the address, the severity, and that the leak is active. Urgency is classified high. Your team gets the summary and decides the response. The service does not promise the homeowner a timeline; that is your call.
Scenario two: tree limb through the roof. A caller reports a punctured deck after high wind. Intake records the structural detail, notes if photos are available, flags it urgent, and notifies you. Whether you tarp tonight or first thing tomorrow is a field decision you make.
Scenario three: routine quote request at 8 p.m. Someone wants pricing on a re-roof. Low urgency. Intake captures scope and callback preference, and it lands in your normal follow-up queue, not your middle-of-the-night alerts.
Scenario four: existing customer, warranty question. A past client asks about a repair under warranty. Intake matches the context, captures the question, and routes it to the right person without waking your on-call tech over something that can wait until morning.
The point: one after-hours line, four very different handling paths, all decided by urgency rules you set.
Storm-call triage boundaries
Triage during a surge means sorting, not solving. A good answering service can classify a call as high, medium, or low urgency based on the words the caller uses and the questions it asks. It can summarize the situation in two lines so you read the queue fast.
What triage is not: it is not a substitute for your judgment, and it does not act in the field. The service does not decide who gets seen first, does not commit your crew to a timeline, and does not assess whether a roof is safe to walk. It captures "active leak, second floor, water spreading" and gets that in front of you. You decide what happens next.
Keep these boundaries explicit with any vendor:
- Classification and summary: in scope.
- Notifying your team on your rules: in scope.
- Arrival times, sending field staff, safety calls, insurance answers: out of scope, always yours.
Sample owner alert fields
When a storm call comes in, the alert your team receives should be skimmable in five seconds. A useful intake record includes:
- Caller name
- Callback number
- Property address
- Reported issue (active leak, missing shingles, wind or hail damage)
- Urgency classification (high / medium / low)
- Two-line summary of what the caller said
- Time received
- New caller or existing customer
- Preferred callback window
- Any access notes the caller volunteered (gate code, dog, blocked driveway)
Notice what is not on that list: a promised ETA, a quoted price, or a dispatch decision. You add those after you read the alert.
Pricing
OnCrew is $49/month for 100 calls, then $0.99 per extra call. It is usage-based, so a quiet month costs little and a storm month scales with the volume that storm created. You can read the full breakdown on the pages below.
Where to go next
If you run a roofing company and want the trade-specific version, start here:
OnCrew for roofers:
https://oncrew.ai/answering/roofers
A deeper resource on roofing answering-service intake:
https://oncrew.ai/resources/roofing-answering-service
Set your urgency rules, define what a high-priority storm call looks like for your crew, and keep pricing, scheduling, and dispatch where they belong: with you.
Disclosure: I am Abe, founder of OnCrew, so read this with that bias in mind. The goal is a useful contractor buying framework, not a claim that one vendor is perfect for every shop.
Top comments (0)