Cold calling guide

How Setters and Closers Share a Call Log (Without Losing Attribution)

Ops playbook for setter→closer handoffs with a shared call log — clean outcomes, ownership, and attribution for any home-services dial floor.

How Setters and Closers Share a Call Log (Without Losing Attribution)

Most home-services dial floors do not fail at dialing. They fail at the handoff. A setter books the sit, a closer owns the close, and somewhere between those two roles the note, the confirmation, and the credit get fuzzy. Learning how setters and closers share a call log is less about software branding and more about one shared truth: who dialed, what happened, who owns the next step, and who gets paid when it lands.

This playbook is for any setter→closer floor — roofing, HVAC, solar, windows, pest, landscaping, insurance, and other high-activity outbound shops. Same physics every time: phone books the appointment, someone confirms it, someone runs the sit, and someone recovers the no-show. If those steps live in three Slack threads and a spreadsheet tab nobody sorted, attribution dies first and revenue follows.


Why shared call logs break on two-role floors

Setter/closer shops create more failure modes than a single-rep dial desk:

  • The setter logs "booked" with no confirmation owner
  • The closer cannot find the note that explained the homeowner's objections
  • Two people call the same lead because ownership was never assigned
  • Spiffs and leaderboards fight because "who booked" vs "who closed" is unclear
  • Confirmations and no-show recovery sit in nobody's morning queue
  • Managers coach dial volume while the real leak is handoff hygiene

A full CRM can still fail here if reps treat it like end-of-day homework. A cold call tracker for sales teams wins when logging is phone-first and the due queue is visible before cold volume starts.

Shared logins make it worse. If every setter uses one account, you cannot tell who booked what — and you cannot coach the right person. One seat per dialer is non-negotiable for honest attribution.


What "shared" should mean (and what it should not)

Shared means one outcome vocabulary, one ownership field, and one due queue the whole floor trusts.

Shared does not mean everyone edits everyone else's notes all day, or that closers dig through a novel of free-text before every sit.

Aim for:

  1. Common outcomes — booked, confirmed, showed, no-show, callback, not interested, wrong number, spouse decide, sent info. Short list. No mushy "talked."
  2. Explicit ownership — setter owns book + first confirmation unless the floor assigns confirmation to an ISA or closer. Write the rule down.
  3. Handoff note in 1–3 lines — pain, timing, spouse involvement, competitor quotes, financing sensitivity. Not a transcript.
  4. Due work that surfaces — confirmation calls and promised callbacks appear on the day they are due. Sticky notes are not a system. Same discipline as a warm lead follow-up system.
  5. Attribution fields that managers can report — booked-by, closed-by, confirmed-by. Without those, your sales leaderboard becomes a fight club.

If your log cannot answer "who owns this lead right now?" in under five seconds, it is not shared — it is shared confusion.


The setter→closer handoff checklist

Use this as the floor standard. Print it. Coach to it.

When the setter books

  • Log outcome as booked (or your exact term) immediately — not after lunch
  • Set confirmation date/time (same day or morning-of, per your process)
  • Assign confirmation owner (default: setter, unless you have a confirmation seat)
  • Write the short handoff note: why they said yes, who else is involved, best call window
  • Tag campaign/source if you run promo or storm lists (helps coaching later)

When confirmation is due

  • Confirmation call or text lands from the assigned owner
  • Outcome updates: confirmed, rescheduled, soft cancel, no answer (with next attempt)
  • If confirmed, closer can see the sit on their day list without hunting Slack

When the closer runs the sit

  • Closer owns show/no-show + close outcome in the same log
  • If no-show, recovery dial is dated (same day + next morning), not "whenever"
  • If close, closed-by is the closer — booked-by stays the setter. Both matter for spiffs.

When something dies

  • Dead reasons are specific: not interested, went with competitor, budget, no decision-maker
  • Do not leave "booked" forever on a ghost appointment. Clean status keeps the queue honest.

This is the same ops muscle as good callback reminder software — dates and owners beat memory.


Outcome vocabulary that setters and closers both trust

Pick 8–12 outcomes and freeze them for 30 days. Example set for home-services dial floors:

OutcomeWho usually sets itWhat it means
No answerSetter/closerAttempt logged; cadence continues
CallbackSetter/closerDated follow-up promised
BookedSetterSit on calendar; needs confirmation ownership
ConfirmedSetter/ISA/closerHomeowner re-affirmed
ShowedCloserSat happened
No-showCloserRecovery queue
ClosedCloserWon
Not interestedEitherDead with reason note
Wrong numberEitherRemove from active dial
Spouse decideEitherDated callback, not a soft dead

Kill "talked," "good call," and "follow up soon" with no date. Those statuses are where attribution and pipeline both go to die.


Spreadsheet vs tracker for setter/closer floors

Sheets can work for one setter and one closer who sit next to each other. They fail when:

  • Three setters overwrite the same "Status" cell
  • Confirmation dates live in a column nobody filters every morning
  • Closers get a text with a name and no note
  • Spiff disputes need a manager archaeology project
  • Seasonal hires cannot find "their" books without breaking filters

If that is your week every promo push or storm surge, you have outgrown the sheet — not the team. Start clean with the free call log template, then move the same fields into a phone-first tracker when volume demands it. Vertical floors hit this early; see the roofing sales call tracker pattern for storm and setter/closer intensity.


How Dialed Sales fits setter→closer ops

Dialed Sales is a cold-call tracker for high-activity teams — not a full CRM. For setter/closer floors that means:

  • Fast outcome logging between dials
  • Due queues so confirmations and callbacks actually appear
  • Per-rep seats so booked-by and activity stay attributable
  • Optional Sara AI for recaps and "who to call next" without replacing the floor
  • Light pricing — see pricing

It is not your proposal tool, route planner, or financing suite. Keep the phone day fast; keep the close system for closes. The handoff lives in the log both roles already trust.


30-day ops plan to fix handoffs

  1. Week 1: Freeze the outcome list. Ban vague statuses in coaching.
  2. Week 1: Write the ownership rule: who confirms, who recovers no-shows.
  3. Week 2: Require a 1–3 line handoff note on every book. Coach incomplete notes the same day.
  4. Week 2: Kill shared logins. One seat per dialer.
  5. Week 3: Morning ritual — due confirmations and callbacks before cold lists.
  6. Week 3: Report books, shows, and closes with booked-by / closed-by visible.
  7. Week 4: Pick the biggest leak (confirmation, no-show recovery, or note quality) and fix only that for two weeks.

Run that for one full promo or storm cycle. You will know whether you need more setters — or just a shared log that keeps ownership honest.


Soft next steps

If you want setter→closer handoffs without CRM bloat:

Either way: one vocabulary, one owner, one due queue. Floors that share a call log well close more of what they already book — they do not just dial louder.


Related: Cold call tracker for sales teams · Warm lead follow-up system · Sales callback reminder software · Roofing sales call tracker · Sales leaderboard for dialing teams

Put every call on rails

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