Roofing warranty calls: Get them off the sales line
The call your sales desk was not built for
A homeowner you replaced a roof for three years ago calls in October. Water is staining the ceiling under a valley. She dials the number on the invoice, which is the number your storm leads call. A CSR who is measured on inspections set picks up, hears "you did our roof," and reaches for the transfer button. There is nobody to transfer to. A note goes to production. Production is on a roof.
Two days later she calls again, angrier. By the third call she has posted the review. The warranty caller is the only person on your phone who has already paid you, and she is the one most likely to be bounced.
Why the warranty call is worth more than it looks
Sales teams treat service calls as cost. The homeowner data says otherwise. Roofing Contractor's 2026 Homeowner Survey found 74% of homeowners find their roofer through word of mouth, and 62% would go back to a contractor they already know. The past customer with a leak is the referral engine for the next roof on her street, or the reason nobody on that street calls you.
Repair work also pays on its own terms. A ticket that a crew closes in half a day carries far less material cost than a replacement, and the caller is not collecting three quotes. That said, the labor picture is tightening. Roofing Contractor's 2026 State of the Industry report found labor costs rose 14% at 55% of contractors, which means throwing a dedicated service team at the problem is not a cheap answer either. The fix is in how calls are sorted, not in how many people sort them.
Three buckets, not two departments
Most operators split calls by who is calling: New prospect or existing customer. That split fails on the call that matters most, because a leak does not care about your CRM status. Sort by what the caller needs instead.
Bucket | Who it includes | What they need | Where it goes |
|---|---|---|---|
New revenue | Prospects with damage, storm callers, retail replacement shoppers | Qualification and a booked inspection | Sales CSR, booked into the CRM on the call |
Active leak, anyone | Past customer or stranger with water coming in now | A same-day tarp or dry-in commitment | Service dispatch, then sales or warranty after it is dry |
Past-customer service | Warranty questions, punch-list items, paperwork, non-urgent repairs | Acknowledgment, a ticket, a date | Service coordinator with a same-day acknowledgment SLA |
The third bucket does the most damage today because it has no owner. The second needs a rule.
The active leak exception
An active leak jumps the queue no matter who is calling. A stranger with water in the living room is a new-revenue call wearing an emergency, and the roofer who gets a tarp on it today is the roofer who writes the replacement. A past customer with water in the living room is a warranty call that turns into a lawsuit or a five-star review depending on the next 24 hours.
The intake question that sorts it is short: Is water coming in right now, or is this something you noticed? If it is coming in now, the call goes to whoever can commit a crew today. Claim status, warranty status, and who pays get sorted after the ceiling is protected. Nobody argues about coverage with a homeowner standing under a drip.
Same-day acknowledgment is the SLA
Warranty callers rarely expect a same-day repair. They expect to be heard the same day. The commitment that holds up is simple: Anyone who calls about a roof you installed gets a human response before close of business, with a ticket number and a date for the next step. That date might be a service visit next week. It is still a date, and it stops the second and third call.
Write the SLA down, measure it, and put someone's name on it. The failure mode is not a coordinator who misses the target. It is a call that never became a ticket because it arrived on the sales queue during a storm week and was logged as a note.
Who should answer the service call
A separate published service number helps at the margin and fails at the core, because past customers call the number they have. The sorting has to happen when the phone is answered, on whatever number the homeowner dialed.
That puts the load on the first 30 seconds of the call. The person or system answering has to recognize a past customer from the CRM, ask the active-leak question, and route to the right bucket without the caller repeating herself. A sales CSR paid on sets will not do this consistently, and it is unfair to ask. A traditional answering service takes a message, which is the outcome you are trying to end.
This is a place where AI intake fits well. An agent that looks up the caller against the CRM, asks whether water is coming in now, opens a service ticket with a same-day callback commitment, and books new inspections into the sales calendar handles the sorting at any volume. Your CSRs keep the new-revenue conversation. Your service coordinator gets a ticket instead of a sticky note. The homeowner who paid you three years ago hears her name, not hold music.
How should roofers handle warranty calls from past customers?
Sort the call by need, not by who is calling. If water is coming in now, dispatch a tarp or dry-in the same day and settle coverage afterward. If it is a non-urgent warranty question or punch-list item, open a ticket and give the homeowner a date before close of business. Past customers drive referrals and repeat work, so a bounced warranty call costs more than the repair would.
Should roofing companies have a separate service phone line?
A separate published number helps a little and fails where it matters, because past customers dial the number on their invoice or yard sign. The sorting has to happen when the call is answered, whatever number was dialed. Recognize the past customer from your CRM, ask whether water is coming in now, and route to service or sales from there. A second number without that triage just adds a second queue.
How do you triage an active leak call?
Ask one question first: Is water coming in right now, or is this something you noticed? An active leak jumps the queue regardless of whether the caller is a past customer or a stranger. Route it to whoever can commit a crew today for a tarp or dry-in, and sort out warranty status, claim status, and who pays after the interior is protected. Coverage arguments can wait. Water cannot.
Do roofing companies make money on repair work?
Yes, on its own terms. A repair carries far less material cost than a replacement, closes in hours rather than days, and the caller is usually not collecting competing quotes. The larger return is indirect. Roofing Contractor's 2026 Homeowner Survey found 74% of homeowners find roofers through word of mouth and 62% would return to a contractor they know. A well-handled repair is how the next replacement on that street gets sourced.
How fast should a roofer respond to a warranty claim?
Acknowledge the same day, before close of business, with a ticket number and a date for the next step. Homeowners rarely expect a same-day repair on a non-urgent warranty issue, but they do expect to be heard the same day, and silence is what produces the second angry call and the public review. If the issue is an active leak, the response is a same-day crew, not a callback.
About Revin
Route warranty calls before they hit sales
Revin answers roofing calls, recognizes past customers, triages active leaks, and books new inspections and service visits into your CRM.
