The Storm Hits Friday. By Monday, You've Already Lost Half the Leads.

Yes — that's the case the auto-reply layer is built for. Whether you get 8 leads or 80 in an hour, every one of them gets the instant template within seconds and lands in your CRM with the customer match already done. The piece you'll feel is on the human side: storm week is when your CSRs and inspectors get buried, and LeadKatch's job is to make sure no lead sits in an unread inbox for six hours while your team is in the field. Most roofers we work with set a separate “storm mode” template they flip on when an event hits — usually a tighter “we're scheduling free inspections in your zip code this week, here's the link” reply.

Honest answer: not yet. Our supported list is Jobber, Housecall Pro, ServiceTitan, and GoHighLevel — those are the four we sync deeply with today. JobNimbus, AccuLynx, RoofLink, and CompanyCam are roofing-specific tools we hear asked about a lot, but we don't want to claim integrations that don't exist. We add new integrations every few weeks and we'll prioritize a roofing CRM if there's enough demand — email us, tell us which one you're on, and we'll be straight about the timeline.

Yes. You can write separate auto-reply templates and route to separate pipelines based on the LSA job category Google passes through plus keyword rules you set (words like “hail,” “claim,” “adjuster,” “deductible” vs. “new roof,” “quote,” “financing”). A claim lead can fire a “we'll work directly with your adjuster” reply and route to your restoration coordinator; a retail lead can fire a financing-options reply and route to sales. The split happens before a human touches the lead.

Anything that lands as a lead source we can capture — LSA, Google Ads, Meta, GBP, website forms — gets attributed automatically. For door-knocking and referrals, your reps tag the source when they create the lead in your CRM, and the same closed-loop math runs from there. EagleView and Hover are a middle case: if their leads come into your CRM as a customer record we'll match and attribute them; if they're sitting in a separate vendor portal we don't pull from, we won't see them. Worth a quick call to map your specific lead flow before you sign up.

Stays out of it, mostly. Supplements are a roofing-specific insurance workflow that lives inside your project-management tool (Xactimate, your CRM's claim module, etc.) and we're not going to pretend we replace that. What we do contribute: the final invoiced revenue we attribute back to the original lead is the actual collected number after supplements settle, not the original contract amount. So your LTV-by-source math reflects real money in the door, not the first signed quote.

For 5 trucks running steady LSA spend, the $249/mo LeadKatch plan is the natural fit — built for the lead volume a mid-size residential shop sees in a normal month, with headroom for storm weeks. If you're earlier in your LSA spend or just testing it, $99/mo Starter works fine and you can move up later. And if Founder seats are still open at $49/mo when you sign up, grab one — full LeadKatch plan, locked at that price for as long as you stay a customer. 50 seats total, then it's gone.

Yes — you can add seats, regions, and routing rules for a temporary operation and then remove them when the work wraps. There's no contract and no setup fee, so a 90-day storm deployment doesn't lock you into anything. Practical caveat: LSA itself has its own state/region setup that lives inside Google's UI, and that part is on you. LeadKatch picks up whatever LSA sends us, so once Google is showing your ads in the new market we're routing those leads from day one.