1. Home
  2. Guides
  3. Real estate ISA teams
  4. Playbook

Playbookfor real estate isa teams

Real estate ISA calling playbook: call blocks, cadence and KPIs

Updated September 28, 20265 min read3 primary sources

An agent on a call at the kitchen island of a staged waterfront home

The short answer

This playbook lays out how a real estate ISA team runs its calling day: the morning speed-to-lead block, the afternoon nurture block, list hygiene before any session, an attempt cadence that respects the lead, a disposition set the licensed agent trusts, and the KPI ranges a team should hold itself to, with DialBreeze production numbers as the reference.

Step by step

  1. 1

    Build the list the night before

    Consolidate overnight web and portal inquiries into one CSV with source, property viewed, submit time and time zone. Apply your internal DNC list and per-lead quiet hours before the session, not during it.

  2. 2

    Run the morning speed-to-lead block

    Start at 9 a.m. in the lead's local time. Work newest first on three lines. Every connected call gets the six-question qualification and a disposition before the next dial.

  3. 3

    Work the callback block after lunch

    Call the leads who asked for a specific time and the morning no-answers. Same script, same fields, and a voicemail drop where nobody picks up.

  4. 4

    Run the nurture block in the late afternoon

    Work leads dispositioned for 60 and 90 day callbacks with their original AI summaries attached. Two removals a week is normal; honor them permanently.

  5. 5

    Review summaries before handoff

    The team lead scans the day's summaries for missing fields and wrong dispositions, checks names and numbers against recordings, and releases the leads to the licensed agents.

What this playbook covers

An ISA team’s output is measured on two things: how fast a new inquiry reaches a real conversation, and whether the licensed agent inherits that conversation prepared. This playbook structures the day around both. It assumes DialBreeze or a similar three-line browser dialer, your own Telnyx numbers, and a team lead who reviews output. It does not assume a call center floor. Three lines per ISA, a human on every answer, and a recording of every connected call is the whole engine.

List hygiene happens before the session

The block starts clean or it does not start. Consolidate overnight inquiries into one CSV the night before with source, property viewed, submit time and time zone on every row. Run your internal DNC list against it. Set per-lead quiet hours by the lead’s clock, not the office clock, because the fastest way to burn a Seattle lead is to call it at 6 a.m. Pacific from a Florida desk. Dedupe across portals, since the same buyer fills out three forms on the same evening and deserves one call, not three.

Attempt caps get set at the list level: three attempts over five days for a fresh inquiry, then a dispositioned cooldown. For any list beyond your own inquiries, scrub against the National Do Not Call Registry at telemarketing.donotcall.gov on the 31-day cycle the rules expect, and keep the evidence. Your own web and portal inquiries generally carry an established business relationship for 90 days under 16 CFR 310.2, but that clock runs from the inquiry, and wireless numbers still carry the TCPA restrictions at 47 CFR 64.1200, which is why every dial here is human-dialed.

The calling day in three blocks

Morning speed-to-lead block, 9:00 to 11:00. Overnight inquiries, newest first, three lines. The target is every lead from the last 24 hours contacted inside the block, with the six-question qualification on every connect and a disposition before the next dial. Voicemails get the recorded drop; the summary marks the attempt.

Callback block, 1:00 to 2:00. Morning no-answers and leads who named a time. This block converts well because the lead already heard from you once. Same script, tighter: “tried you this morning about the Pine Street listing.”

Nurture block, 4:00 to 5:00. Leads dispositioned 60 and 90 days out, called with their original summaries attached. The opener references the actual last conversation: “you mentioned your lease ends in March.” Two or three removals a week is the normal cost of this block; the do-not-call disposition drops them from every future list, which is the point.

Attempt cadence that respects the lead

Fresh inquiry: attempt one inside 24 hours, attempt two the next day at a different hour, attempt three within five days, then disposition and stop. A lead that never answered three varied attempts is not a bad lead, it is a voicemail lead, and the fourth attempt same-week is how teams generate complaints. Nurture leads get one attempt per cycle. Nobody gets called twice in one day across two lists, which is what dedupe and attempt caps are for.

Dispositions the licensed agent can act on

Appointment set, agent callback, callback later with a date, nurture with a cycle, already has an agent, left voicemail, no answer, wrong number, do not call. Nine dispositions, no more. The disposition is a filter; the detail lives in the AI summary. When a disposition is ambiguous, fix the summary habit, not the disposition list, because a twenty-item list means ISAs guess and agents stop trusting the field.

Running three lines and the AI summaries

Three lines per ISA means the voicemail layer stops eating the morning. The ISA takes the first live answer; the other lines ring out or take the recorded drop. Watch abandoned-call counts weekly and drop to two lines if answer detection keeps outrunning the ISA.

After each connected call, DialBreeze transcribes the recording and writes the summary: intent, areas, criteria, financing, timeline, objection, next step. The ISA checks names and numbers against the recording before the next dial, a habit that takes ten seconds and saves the agent from calling “Steven” as “Stephan.” The team lead reviews summaries in batches before releasing leads to agents, and pulls two recordings per ISA per week for coaching: one booked appointment, one objection call.

KPI ranges and the production benchmark

Set targets as ranges, then judge against your own trend.

  • Dials per active calling hour: hold 70 to 100, with a median of roughly 85 measured in DialBreeze production use, 3-line sessions, over 90 days. Below 60 for a full week means the block has a wrap-time problem, not an effort problem.
  • Dials per ISA day: plan 450 to 700, with roughly 600 as the production median for a full operator day. A two-block morning plus afternoon work should land an ISA near the middle of that range.
  • Person-connect rate: plan 12 to 22 percent of dials, with 17.8 percent as the production median. Track per block: morning portal lists connect differently than 90-day nurture lists.
  • Appointments per week: set your own target from your own first four weeks. Team contexts vary enough that any published number would be invented.
  • Speed to lead: first attempt inside 24 hours on 95 percent of new inquiries. This is the one number with no asterisks.

The DialBreeze figures come from 37,411 dials, 17,645 recordings and 9,367 AI summaries over 90 days to 2026-09-26, aggregate production activity, not customer results, and not a promise about your list.

Compliance checklist for the ISA desk

Calling hours 8 a.m. to 9 p.m. at the lead’s location, enforced per lead. Internal DNC honored permanently, registry scrubbing on the 31-day cycle where the list is not your own inquiry. A recording disclosure your broker approved, especially into all-party consent states. ISAs kept on qualification and scheduling, with price and contract talk left to licensed agents under your state’s license law. No product, including this one, makes an outreach lawful; the rules live at 47 CFR 64.1200 and the FTC’s Telemarketing Sales Rule, and the team owns them. Nothing here is legal advice; run the program past your broker and, where the lists get creative, counsel.

FAQ

How many dials should one ISA make in a morning block?
Hold a range of 70 to 100 dials per active calling hour as healthy on three lines, with a median of roughly 85 measured in DialBreeze production use over 90 days. A two-hour morning block should therefore land between 140 and 200 attempts if the ISA is actually dialing, not wrapping.
What person-connect rate should an ISA expect?
Plan around 12 to 22 percent of dials reaching a live person, with 17.8 percent as the production median over the same 90 day window. Connect rate swings with list quality and time of day, so track it per block rather than judging an ISA on a single week.
How do three lines work without abandoned calls?
Three lines ring at once and the ISA takes the first answer. Answer detection can be wrong and two people can answer at once, so pick the line count your ISAs can actually handle, keep ring time modest, and watch abandoned calls weekly. DialBreeze caps concurrency per seat by design.
What belongs in list hygiene before a session?
Your internal DNC list, per-lead quiet hours based on the lead's time zone, attempt caps, and dedupe across sources because the same lead arrives from three portals. Registry scrubbing applies to any list outside your own inquiries.
How does the agent handoff actually work?
Disposition plus task plus AI summary. The ISA sets 'Appointment set' or 'Agent callback' with a time, and the agent opens the lead to read the summary and play the part of the recording that matters. No separate handoff note unless the ISA wants one.

Sources

  1. ecfr.gov /current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200
  2. law.cornell.edu /cfr/text/16/310.2
  3. telemarketing.donotcall.gov /

Operational guidance, not legal advice. Rules vary by state and by campaign.

Put the script to work.

Three lines, a recording of every connected call and the notes written after you hang up.

Start a 14-day trialPricing