Cold calling guide

How to Protect Attribution During a Storm Blitz (Booked-By and Closed-By That Stay Honest)

When storm season floods the dial floor with new setters and hot leads, credit gets messy fast. Here's how to keep booked-by and closed-by honest so pay, coaching, and spiffs stay fair.

A hail or wind event hits, the phones light up, and within a week your dial floor has doubled. Seasonal setters are logging in for the first time, closers are running back-to-back inspections, and leads are coming from door knocks, web forms, referrals, and old lists all at once. It's the best revenue window of the year. It's also when attribution falls apart.

Two weeks later, payroll asks who booked what. Three setters claim the same signed roof. A closer swears a deal was self-generated. The new hire who actually set the appointment is about to quit because their board shows zero. None of this is about bad people. It's about a storm surge running through a system that was built for normal volume.

This guide is for roofing, siding, gutter, and other exterior home-services teams (and any outbound floor that surges seasonally) that want booked-by and closed-by credit to stay honest during a blitz. It covers the rules to set before the storm, what to log on every call, how to handle the edge cases that cause fights, and how to review credit weekly so it never piles up.


Why attribution breaks during a storm blitz

Normal weeks hide weak attribution because there's less overlap. During a blitz, everything overlaps:

  1. The same homeowner gets touched by multiple people. A canvasser knocks, a setter calls the web form, and a closer drives past and stops in. Who gets credit?
  2. Seasonal setters share seats or logins. When three temps use one account, every booking looks like it came from the same person.
  3. Leads arrive from many sources. Door, phone, referral, insurance adjuster, and old list rows all land in different places, so nobody can see the first real touch.
  4. Reassignments happen fast and quietly. A closer gets sick, an inspection moves to someone else, and the original booking credit gets overwritten.
  5. Credit is reconstructed after the fact. If you wait until commission day to figure it out, you're relying on memory and whoever argues loudest.

The fix isn't a heavier CRM. It's a few clear rules, decided before the surge, and a call log that records them as calls happen.


Step 1: Write the credit rules before the first storm call

Attribution fights are really rule fights. If nobody wrote down what "booked" means, everyone fills in the version that pays them best. Settle these in a one-page doc and read it out at the first blitz standup:

QuestionRecommended rule
What counts as "booked"?A confirmed inspection or appointment with a date, time, and address, logged with the booking setter's name
Who gets booked-by credit?The person who set the confirmed appointment, not the first person who ever touched the lead
What if two people touched the lead?Booked-by goes to whoever logged the confirmed appointment; earlier touches are noted but not credited
What counts as "closed"?Signed contract or approved insurance claim scope, logged with the closer's name
What if the closer changes?Closed-by goes to who signed it; booked-by never changes once logged
What about self-generated deals?Allowed only if no setter booking exists in the log for that address or phone
How long does booking credit last?Set a window (for example 30 or 60 days) so old bookings don't claim future re-sets

The exact rules matter less than writing them down and applying them the same way for everyone. If you've already debated this on calmer weeks, reuse that work. Our guide on how to attribute books vs closes fairly goes deeper on the general rules; the storm version just needs them locked earlier and enforced harder.


Step 2: Give every setter their own seat, even temps

Shared logins are the single biggest source of storm-season attribution fights. If three seasonal setters dial from one account, you can't tell who booked what, you can't coach them, and you can't pay them fairly.

Before the blitz:

  • Create a seat for every person who will dial, including temps who might only last a week.
  • Make it fast to add and remove people. If onboarding a new setter takes a day, managers will share logins out of desperation.
  • Never reassign a seat to a new person mid-blitz. Close the old one and create a new one so history stays with the right name.

If your current tool makes this painful, that's worth fixing before storm season rather than during it. Teams running multiple reps through one account usually find multi-rep call tracking without shared logins solves most of the arguments on its own.


Step 3: Log the four fields that settle every dispute

You don't need twenty fields to protect attribution. You need four, logged at the moment of the call, not reconstructed later:

  1. Lead source. Door knock, storm web form, referral, adjuster, old list, inbound call. Pick from a short fixed list.
  2. Outcome. Booked, callback, no answer, not interested, already hired, bad number. Again, a fixed list.
  3. Booked-by. Auto-filled from the seat that logged the booking. Nobody should type someone else's name.
  4. Closed-by. Filled when the deal signs, by the closer or manager, from the same log.

Everything else is helpful context (roof age, insurance carrier, adjuster date), but these four are what you'll need on commission day. If your setters are new, give them the free call log template as a reference so they know exactly what a complete entry looks like.

A good test: could someone who wasn't on the floor that day read the log and say who booked and who closed every signed deal? If not, a field is missing or isn't being filled in.


Step 4: Handle the edge cases before they become fights

Storm blitzes generate the same handful of disputes every year. Decide them in advance:

The canvasser knocked, the setter booked by phone. If your canvassers and setters are paid differently, decide whether the knock earns a separate "lead generated" credit. Keep it separate from booked-by so it doesn't muddy setter numbers.

The homeowner called back in and anyone answered. Whoever confirms the appointment gets booked-by, but log the original setter in the notes. If this happens a lot, route inbound callbacks to the original setter when they're on shift.

The appointment no-showed and someone else re-booked it. Most teams credit the re-booker, since they did the work that produced a sit. Whatever you choose, write it down.

The closer reassigned the inspection. Booked-by stays put. Closed-by goes to whoever signs. Log the reassignment so the original closer's sit count makes sense in coaching.

The lead was already in an old list. If a setter calls an old list row and books it, they get the credit. An old row nobody worked doesn't belong to anyone.

Duplicates across channels. The same homeowner can show up as a door lead and a web form lead with slightly different names. Search by phone and address before creating a new row, and merge to the earliest record.


Step 5: Review credit every week, not on commission day

The worst time to sort out attribution is when money is on the line and memories are fuzzy. During a blitz, run a short weekly credit check:

CheckWhat you're looking for
Bookings with no booked-by nameMissed logs or shared-seat entries to fix now
Signed deals with no matching bookingPossible self-gens, or bookings that were never logged
Same address booked by two settersDuplicate rows to merge and a rule to apply
Setters with high dials and zero booksCoaching need, or bookings being logged under someone else
Closers with sits but no booked-by on themInspections that skipped the log entirely

Fix issues the same week. Each fix should take minutes when it's fresh and can take hours once three weeks of storm calls pile up. A weekly review also tells seasonal setters their work is being seen, which matters for keeping them through the surge.

For the broader storm workflow these checks plug into, see the roofing storm blitz call ops checklist and the storm lead follow-up system.


Step 6: Keep the leaderboard honest

Storm-season leaderboards are great for energy and terrible for attribution if they reward the wrong thing. A few guardrails:

  • Rank on confirmed bookings and sits held, not raw dials. Dials alone reward speed over quality and push people to grab credit.
  • Show booked-by and closed-by separately. Setters shouldn't compete with closers on the same board.
  • Only count entries that pass the weekly check. If a booking can't be tied to a seat, it doesn't go on the board.
  • Pay spiffs from the log, not from claims. If it isn't logged with a name, it didn't happen for spiff purposes.

When the leaderboard and the payout come from the same log, people stop arguing and start logging carefully, because that's how they get paid.


A simple storm attribution checklist

Before the blitz:

  • Credit rules written and shared
  • A seat for every setter, temps included
  • Fixed lists for lead source and outcome
  • Booked-by auto-filled from the seat

During the blitz:

  • Every call logged at the moment it happens
  • Phone and address searched before new rows are created
  • Reassignments logged, booked-by never overwritten
  • Weekly credit check with same-week fixes

After the blitz:

  • Final credit report pulled from the log
  • Disputes settled against the written rules
  • Rules updated for next season based on what came up

How Dialed Sales helps

Dialed Sales is a phone-first cold-call tracker built for high-activity floors like roofing, solar, and HVAC. Every rep gets their own seat, every call gets an outcome and a due time, and booked-by is recorded from the person who logged it. During a storm surge, that means you can add seasonal setters quickly, see who booked and who closed every deal, and run a weekly credit check from one log instead of piecing it together from texts and spreadsheets. Sara AI can summarize the week's bookings and gaps so the review takes minutes.

If storm season is coming and your attribution still lives in group chats, try Dialed Sales before the next weather event and give every setter a clean seat from day one.

Put every call on rails

Log a call in seconds, get follow-ups surfaced the day they're due, and keep a live leaderboard.