Benefits broker power dial playbook: call blocks, cadence and KPIs

The call block, in three shifts

Benefits prospecting fails when the list is one undifferentiated pile. Split the day into three blocks with different jobs.

Morning block, new prospects. Renewals inside 120 days come first, then referral names, then cold rows from a sourced list. This is the block where you will hit the most gatekeepers, so it is also where you record the best routing information. Expect a lot of voicemail; that is normal and it is not failure.

Midday block, follow-ups. Everyone who asked for a comparison, everyone who said call me after the first of the month, and every capability email you sent. Follow-ups convert better than new dials, and they are easy to skip when the day gets short. Do not skip them.

Late block, referrals and gatekeepers. Call back the people the front desk told you to call but who were unavailable in the morning, and dial the direct lines you collected. This block also catches owners who are only at their desk late.

List hygiene

Keep the source column populated. A chamber list, a referral from a client, and a scraped row without provenance are three different compliance objects even if they look identical in a spreadsheet. Strip anything on your internal do-not-call list before the block loads, not during the session.

Deduplicate by phone number, not by company name, so a company that appears on three lists does not receive three attempts. If your producers each keep a private list, merge them weekly. Duplicate outreach is the most common complaint driver in small brokerages.

Attempt cadence

This is the part that separates a professional phone operation from a nuisance. A workable cadence for a benefits list:

• Attempt 1, day 1. Open the record. Ask for the benefits owner and the renewal month.
• Attempt 2, day 3. Reference nothing if you only reached voicemail, and reference the prior attempt if a human answered.
• Attempt 3, day 7. Different time of day on purpose. Morning if the first two were afternoons.
• Attempt 4, day 10. Ask directly whether you should close the file, which often gets a real answer.
• Then close the record for 90 days unless the contact asked you to stop, in which case it leaves every queue permanently.

Two rules sit on top of the cadence. First, a stop request outranks everything and goes into the suppression list the same day. Second, quiet hours are set to the contact’s local time, not your office time.

Dispositions that mean something

Generic outcomes (“interested,” “not interested”) do not tell a producer what to do next. Use a set that maps to renewal stages:

• Renewal discovery booked: put the date on the record.
• Send capabilities: attach the one-pager and date a follow-up call.
• Got referral: record the name and the correct extension.
• Renewal too far out: dated callback six months before renewal.
• Current broker retained: long callback at the next cycle.
• Not a fit: remove from active prospecting.
• Do not call: permanent suppression.

Working the three lines

DialBreeze rings up to three numbers at once for one producer. The producer takes the live answer and the recorded voicemail drops on the other lines with one key. That changes the shape of the block: instead of listening to rings, most of the hour is conversation.

Two practical points. Answer detection is not perfect, and two people can answer at the same time. Pick a line count the producer can handle without dropping a real conversation. And because the AI summary is built from the recording, the calls worth summarizing need to be recorded. Use a recording disclosure at the start of the call, since several states require every party to agree before recording and a benefits call often crosses state lines. TCPA limits on prerecorded messages to wireless numbers also apply, and the FTC business-to-business exemption in 16 CFR 310.6(b)(7) does not dissolve the rest of 47 CFR 64.1200.

Where the AI summaries go

The summary is not the CRM entry. It is the raw material for it. Once a day, read the summaries from the block and do three things: move the agreed next step into the CRM with a date, check the carrier and renewal fields against the recording, and note any claim or health detail into the firm’s approved system rather than a general-purpose note field. Small health details in the wrong system is a privacy problem you do not want to have.

KPI targets as ranges

Use ranges, and use them against your own history rather than as absolutes. Reference points measured in DialBreeze production use (last 90 days to 2026-09-26, three-line sessions): a median of about 85 dials per active calling hour and about 600 dials per operator day, with a 17.8 percent person-connect rate. That is the shape of the tool when a real list runs, not a promise for your list.

For benefits work specifically, watch these:

• Dials per active hour: 70 to 100 keeps a three-line session honest.
• Person-connect rate: expect roughly 12 to 20 percent on cold business lists, higher on referrals.
• Meetings booked per producer-week: 3 to 8 is a healthy range for a producer running three blocks a day.
• Meetings held over meetings booked: above 70 percent means the meeting ask is genuine.
• Disposition completeness: 100 percent. There is no acceptable blank.

Compliance checks that stay inside the workflow

Keep the suppression list live across every list you load, set quiet hours per contact’s local time, use a recording disclosure, and keep producer licenses current in each state where you advise. Business-to-business calling sits mostly outside the FTC Telemarketing Sales Rule, but entity-specific stop requests are absolute and TCPA wireless-number rules still apply. For anything involving health information or state licensing questions, get your own counsel involved. This playbook is an operating guide, not legal advice.