The short answer
This playbook covers how a wholesaling operation runs its calling: new source records worked inside a day, written-number callbacks with repair math, fell-through recontacts, list hygiene with source documentation, cadence rules, dispositions, three-line sessions with AI summaries, and the KPI ranges that keep the pipeline honest.
Step by step
- 1
Load only records with documented sources
Every row carries its source and the consent basis. Screen out flagged numbers, dedupe across list purchases, and apply your internal DNC list before the session. A record with no source is a problem before the first call.
- 2
Work new source records inside a day
Call while the reason the record exists is still current. The opener names the address and the reason; five questions decide whether a deal exists.
- 3
Run the written-number callback block
Sellers who asked for a number get a range with the repair logic attached, presented on a call or in writing as agreed. The task ships with the disposition, same block.
- 4
Work the fell-through recontact list
Deals that died during diligence are the warmest calls in the queue: the seller has been through the process and knows the numbers. Call with the original summary attached.
- 5
Review records and next actions before the block ends
Verify condition, title and price fields against recordings. Every warm seller leaves the block with a dated next action, and the disposition lead gets the list.
What this playbook covers
The phone work in wholesaling is straightforward: find sellers with a problem, qualify the property, put a contract on it. What surrounds that work is a patchwork of state rules about who may market a property and what must be disclosed, and a federal calling framework that treats every owner as a consumer. This playbook structures the calling so the phone work is disciplined and the surrounding rules are respected. It assumes a three-line browser dialer on your own Telnyx numbers, a caller doing the talking, and recordings with after-call AI summaries.
List hygiene and the source field
Only records with documented sources get loaded: the source and the consent basis ride on every row. A purchased file with no origin story is a problem before the first call, and the list policy that accepts it owns whatever follows. Dedupe across list purchases, because the same address arrives on three lists, and the owner notices the second call more than the first. Your internal DNC list applies to everything, quiet hours run on the owner’s clock, and registry scrubbing runs on the 31-day cycle for anything that is not a permissioned callback.
Wholesaling outreach is residential solicitation: calls run 8 a.m. to 9 p.m. at the owner’s location under 16 CFR 310.4(c) and 47 CFR 64.1200(c)(1), and a revocation made by any reasonable means must be honored within ten business days under 47 CFR 64.1200(a)(10).
The calling week in blocks
New source record block, daily. Records called inside a day of arrival, while the reason is current. The opener names the address and the reason; five questions, condition, occupancy, timeline, price expectation, title, decide whether a deal exists; the disposition routes the record into the funnel or out of it.
Written-number callback block, as tasks come due. Sellers who asked for a number get a range with the repair math attached. The presentation happens on a scheduled call or in writing as agreed, and the task ships with the disposition, because a promised number that never arrives is both a lost record and a complaint risk. The comp the seller is holding gets addressed line by line, with the listing route named honestly as the alternative.
Fell-through re-contact block, weekly. A deal that died in diligence is a seller who has been through the numbers already: the warmest call in the queue. The original summary carries what stalled it, the title question, the partner disagreement, and the re-contact opens with that reason. Some of these sellers list with agents, which is a fine outcome and a relationship worth keeping.
Partner-agreement follow-up, as needed. Sellers who need a spouse or a sibling on board get one structured call, then a dated re-entry after the conversation happens at home. “Needs partner agreement” with a date is a live record; without one it is a graveyard.
Attempt cadence that keeps the list callable
New records: attempt one inside a day, attempt two a few days later at a different hour, then a dispositioned stop or a dated re-entry. Written-number waits: one reminder call after the agreed time, then a re-entry. No owner hears a fourth voicemail in a month, and no owner who said stop hears anything again. Attempt caps make the policy automatic, and in a trade with this much regulator attention, the cadence is part of the compliance posture.
Dispositions that keep the funnel honest
Appointment set, wants a written number, needs partner agreement, title issue follow-up, not selling remove from campaign, do not call permanently, wrong number or unverified owner. Title issues deserve their own disposition because they are a research task, not a dead lead. Every warm seller leaves the block with a dated next action, and the disposition lead receives the list before the block ends; that handoff is the discipline step that separates offices that scale from offices that stall.
Three lines and the AI summary workflow
Three lines clear the voicemail layer on owner lists, which is where most of the block would otherwise die. After each connect, the AI writes the transcript and pulls the fields: occupancy, condition, title signals, timeline with the reason, price expectation with the comp behind it, next step. The caller verifies condition and title answers against the recording before the next dial, because the offer’s repair math rides on those two fields, and a misheard comp poisons the written number.
The weekly review pairs summaries with outcomes: written offers requested versus delivered, title issues resolved versus stalled, and the source-field audit, which sources produce engaged sellers and which produce complaints. That audit is the list policy’s feedback loop.
KPI ranges and the production benchmark
- Dials per active calling hour: 70 to 100, median near 85 in DialBreeze production use, 3-line sessions, 90 days.
- Dials per caller day: 400 to 700 for a full day of blocks; most operations run two to three blocks, landing 200 to 400.
- Person-connect rate: 12 to 22 percent planned, 17.8 percent production median; measure sources separately.
- Written offers requested per week: the leading indicator, tracked against attempts and connects with clean denominators.
- Contracts signed per month: your own number, from your own sources and market.
The production figures come from 37,411 dials over 90 days to 2026-09-26 in DialBreeze operation, aggregate activity, not customer results and not a promise about your list. The internal window is an activity record, not a promise about disposition rates.
Compliance checklist for the wholesaling desk
Calling hours, registry scrubbing, entity-specific stop requests, revocation honoring inside ten business days, all under 47 CFR 64.1200 and the FTC rule. All-party recording consent in the states that require it. The state layer on top: marketing a property you do not own is regulated or prohibited in several states, with disclosure and licensing requirements, so confirm the position before the first contract, not after. And if referral fees enter the picture, 12 U.S.C. 2607 prohibits paying for referrals of settlement service business on federally related mortgage loans. Nothing here is legal advice; this desk runs on counsel-reviewed list policy and state-specific contracts.
FAQ
How many dials should a wholesaler make per block?
What connect rate should a seller list produce?
How many attempts does a seller get?
Which number is the leading indicator?
What compliance layers are specific to wholesaling?
Sources
- law.cornell.edu /cfr/text/16/310.4
- law.cornell.edu /cfr/text/47/64.1200
- law.cornell.edu /uscode/text/12/2607
Operational guidance, not legal advice. Rules vary by state and by campaign.