Mortgage broker calling playbook: team blocks, cadence and KPI ranges

The call block, in three shifts

A broker team has a coordination problem on top of a calling problem, and the block structure solves the coordination first.

Morning, warm pipeline sweep. Records no one has touched in 14 days, sorted by file stage and decision date. The call references the relationship and asks one question: what changed since the last conversation.

Midday, document recovery. Processors call the files with missing items, name the exact documents and attach due dates. This block moves files more than any other, and it is the one that dies when the floor gets busy. Protect it.

Afternoon, partner and past-client block. Realtor partner updates on active files, and past-client reviews that produce referrals. These calls are relationship maintenance with pipeline effects, and they use a different tone from the morning block.

The three blocks belong to different roles where staffing allows, and forcing them onto one person in one sitting is how a team ends up with three half-finished lists. A coordinator owns the sweep, a processor owns document recovery, and the team lead or the officer’s assistant owns partner care. Where two people cover everything, split by block rather than by borrower, because a borrower with one caller and one paper trail forgives a lot, and a borrower who hears two voices from the same brokerage in a day forgives nothing.

List hygiene: ownership and consent on every row

Load records with borrower, phone, file stage, assigned officer, missing items, decision date and the consent basis for contact. Assign the owner before the block. The consent basis is doing legal work: it defines who may be called and about what, and a record whose basis is unclear routes to the compliance question, not to the dial queue.

Deduplicate by phone and name, because the same borrower appears in the lead system, the LOS export and a partner email thread. Screen the internal do-not-call list before the block, and refresh National Do Not Call Registry scrubbing at least every 31 days. Consumer calls stay inside 8 a.m. to 9 p.m. local time at the borrower’s location under 16 CFR 310.4(c) and 47 CFR 64.1200(c)(1), with revocations honored within a reasonable time not to exceed ten business days.

Attempt cadence

Three touches per week per record, then escalation or park.

• Day 1: the callback, with the specific question or item named.
• Day 3: the reminder, with the checklist or letter resent.
• Day 5: officer escalation where the file warrants it, or a dated park.
• Quiet hours follow the borrower’s local time, not the office’s.

Pipeline borrowers expect responsiveness, not persistence. The cadence is short because the relationship already exists, and a fourth unanswered touch reads as pressure from a company the borrower trusted with a loan application.

Dispositions in team terms

• Documents requested: items and due date.
• Rate call booked: officer, day, time.
• Appointment set: attendees.
• Scenario changed: what moved.
• Needs time: follow-up month.
• Withdrawn or funded elsewhere: with the reason.
• Duplicate or reassigned record: fixed ownership, logged.
• Do not call permanently.

Working three lines on a pipeline list

DialBreeze rings up to three numbers per operator and the operator takes the live answer, with a recorded voicemail dropping on the rest. Pipeline lists connect high because the relationship exists, so the right line count is the one the team can serve without stacking two borrowers at once. Recording feeds the AI summary; several states require all parties to consent, including Washington under RCW 9.73.030 and California under Penal Code 632, so keep a disclosure. DialBreeze applies your internal lists, quiet hours and attempt caps; it does not decide whether a number may be called.

Where the AI summaries go

The summary is what makes a team function as one company. Scenario, missing documents, decision date, co-borrower availability and the booked step, written the same way by every operator, so the officer’s call starts informed and the processor’s queue stays accurate. Verify lock dates, dollar figures and document lists against the recording before they drive anything, because a misheard number in a borrower file becomes a complaint with a transcript. The summary is a working note; it does not clear a file, make an underwriting decision or replace the officer’s records. Borrower financial information also makes GLBA privacy obligations relevant to how summaries and recordings move between team members.

KPI targets as ranges

Reference points measured in DialBreeze production use (last 90 days to 2026-09-26, three-line sessions, one operator per session): median of about 85 dials per active calling hour, about 600 dials per operator day, and a 17.8 percent person-connect rate. Aggregate measured values, not a promise.

For a broker team:

• Dials per operator day: measured median about 600 per day on three lines.
• Person-connect rate: 17.8 percent measured over the last 30 days in production use; your list mix will move it.
• Files moved per operator-week: track it weekly and set the target from your own first two weeks of data. Records advanced by a disposition.
• Document recovery within 48 hours:
• Duplicate-contact incidents: tracked weekly, target zero.
• Realtor partner touches per active file: at least one per two weeks while under contract.

Compliance, disclosure and the parts that belong to counsel

Every consumer rule applies per record, and team structures multiply the supervision duties rather than dividing them. State licensing rules put rate and loan-term conversations with licensed personnel, GLBA privacy governs how borrower data moves, consent travels with the record through every reassignment, and all-party recording consent states shape the disclosure. Keep the ownership field honest, route anything about marketing to borrowers versus servicing them to counsel, and treat this playbook as an operating guide, not legal advice.