First-party AR power dial playbook: blocks, cadence and policy review

Counsel review notice

This playbook describes how a first-party billing or AR team could operate a calling program. It is explicitly conditional because the legal position depends on facts your organization owns: whether the accounts are commercial or consumer, whether medical services are involved, which state laws apply, and how your privacy review treats service detail. Have counsel review the script, the voicemail policy, the retention rules and the data path before any calls are placed. Do not dial patients or consumers first and review afterward.

The call block, in two shifts

AR calling has a natural shape: the value is in the promise and the promise is only worth something if it is kept.

Afternoon, working block. Balances needing a first contact, segmented by age. A 35-day invoice gets a reminder tone; a 95-day invoice gets a firmer one and a written notice schedule. This block also handles statement and invoice-copy requests.

Late morning, promise block. Every promise-to-pay with a date arriving today or tomorrow, plus accounts where a payment was expected and did not arrive. This block is quiet, unglamorous, and it collects more per hour than the working block.

List hygiene and segmentation

Load the aging export as a CSV: customer, invoice number, invoice date, original amount, current balance, last payment date and contact history. Segment into 0 to 30, 31 to 60, 61 to 90 and over 90 days. The tone, the ask and the payment options differ by segment, and a specialist who knows the segment does not have to think about it mid-call.

Suppress accounts with a recent payment that has not posted, accounts in a documented dispute review, accounts on the internal do-not-call list, and any account your policy has removed from calling. Deduplicate by customer so three invoices do not produce three calls to the same AP contact.

Attempt cadence

Four touches over three weeks, then move to the next process rather than continuing to dial.

• Touch 1, first contact: verify identity, confirm the invoices, ask for payment in full or a dated commitment.
• Touch 2, documents: send invoices and a statement, confirm the dispute position.
• Touch 3, promise confirmation: the promise date is here, confirm or reschedule.
• Touch 4, written notice step: per policy, with the response window stated.
• Then route the account to the next internal process, which may be a payment plan, a hardship review or a referral out.

Calling hours follow the applicable rules for the account type. For third-party consumer collections, Regulation F at 12 CFR 1006.6 treats times before 8:00 a.m. and after 9:00 p.m. local time at the consumer’s location as inconvenient, and your own policy should be at least that conservative for consumer accounts.

Dispositions by payment stage

• Promise to pay: date, amount and method.
• Paid: with confirmation.
• Payment plan: schedule plus written confirmation sent.
• Invoice disputed: line item and review deadline.
• Hardship referral: routed to the right workflow the same day.
• Insurance pending: payer and expected date.
• Wrong contact: remove the record.
• Do not call: permanent suppression.

Working three lines on an AR file

DialBreeze rings up to three numbers per specialist and the specialist takes the live answer, with a recorded voicemail dropping on the rest. On a commercial AR file many dials reach an accounts payable line or voicemail, so three lines buys more conversations per hour.

Voicemail is where the most risk lives. Follow the written policy exactly, and for consumer accounts, especially medical ones, keep the message to a name, a callback number and a neutral request to return the call. No balance, no service detail. Because AI summaries come from recordings, the calls worth summarizing need recording, and several states require every party to consent before recording, so disclose when you record.

The dialing rules do not disappear because the account is first-party. TCPA restrictions on autodialed and prerecorded calls to wireless numbers under 47 CFR 64.1200 can apply, and the FDCPA framework at 15 U.S.C. 1692a and Regulation F definitions at 12 CFR 1006.2 are the right starting point for understanding which rules may attach if accounts are ever referred out. DialBreeze applies your internal lists, quiet hours and attempt caps; it does not decide whether an account may be called.

Where the AI summaries go

Keep the summary thin and operational: account, contact, amount discussed, promise date, dispute detail, documents requested. The summary should drive the next action, not carry service history. If the account involves medical services, the fields should mirror what your privacy review permits. Verify amounts and dates against the recording before a note changes a payment schedule, because a promise recorded as a different figure will produce a wrong follow-up.

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. Those are aggregate measured numbers, not a promise.

For a first-party AR desk:

• Dials per active hour: 70 to 100 on three lines.
• Person-connect rate: higher on commercial AP files than on consumer lists, so use your own baseline.
• Promises kept over promises made: the single most important internal metric.
• Dollars collected over dollars promised: the lagging version of the same signal.
• Dispute routing same day: a process metric worth watching weekly, because disputes left open become write-offs.
• Disposition completeness: 100 percent.

Policy, privacy and the parts that belong to counsel

Three reviews belong outside this playbook. First, counsel should confirm how the FDCPA framework at 15 U.S.C. 1692a and Regulation F at 12 CFR 1006.2 and 12 CFR 1006.6 apply to your specific account mix, and which state medical debt and billing rules add requirements. Second, your privacy function should approve what may be said on a call and in a voicemail when service or clinical detail exists. Third, state recording law governs whether calls may be recorded and whether all parties must consent.

This is an operating guide. It is not legal advice, and it is not a substitute for those reviews.