First-party AR payment call script with identity verification first

Counsel review notice

This page is an operating guide for a first-party billing or AR team, and it is a conditional fit for a reason. Even though the FDCPA generally targets third-party collectors, medical debt, state collection rules, consumer privacy law and your organization’s own policies can apply to calls about the organization’s own receivables, and the analysis differs for commercial and consumer accounts. Have counsel review the program, the scripts, the voicemail policy and the data handling before any calls are placed. Nothing here is legal advice.

What the first-party AR call is for

A first-party AR call has one job: turn a past-due invoice into a dated commitment. It is not a collections call in the third-party sense, and it should not sound like one. The customer already has a relationship with you, which means the conversation can be plain and specific rather than adversarial.

Two things make it work. Identity verification before any balance is discussed, and a clean separation between what the customer accepts and what they dispute.

Before you dial: policy first, list second

Before a single call, get written answers to these questions. Which balances may be called and which must be routed elsewhere. Who may be contacted about the account. What may be said on a voicemail. How medical or service detail is handled. When an account moves out of first-party handling into another process.

Then build the list. Load the aging export with customer, balance, invoice number, invoice date, last payment date and contact history. Apply the suppression list before the block, not during it.

On the dialing rules: the FDCPA definition of a debt collector at 15 U.S.C. 1692a centers on collecting debts owed to another, which is why a creditor collecting its own debt is generally outside it. Regulation F, at 12 CFR 1006.2, contains the definitions that govern third-party collectors, and 12 CFR 1006.6 governs when and where communications may occur, treating times before 8:00 a.m. and after 9:00 p.m. local time at the consumer’s location as inconvenient. TCPA restrictions on autodialed and prerecorded calls to wireless numbers under 47 CFR 64.1200 can apply regardless of first-party status. DialBreeze applies your internal lists, quiet hours and attempt caps; it does not decide whether a given account may be called.

The opening: verify before you discuss

“Hi, this is Angela in accounts receivable at Corvane Supply. Before I go any further, I need to confirm I am speaking with the right person. Can you confirm your company name and the last four of the account number on your statement?”

This is not a formality. Disclosure of a balance to an unauthorized person creates a privacy problem, and in a healthcare context it can be a protected health information problem. Verify first, then talk numbers.

The talk track, in order

The script above runs verify, confirm, split, commit. Three habits make it work.

First, lead with the invoice numbers and offer to send copies. Customers who feel ambushed by a number they cannot verify will dispute on principle. Customers holding the invoice will usually tell you which parts are real.

Second, split the balance the moment a dispute appears. Take the undisputed portion and move the disputed line item into a review with a named response time. That converts an argument into a partially collected invoice.

Third, end on a written confirmation. The commitment date is worth little if it lives only in your notes, and a statement email that matches the customer’s records prevents the next call from starting at zero.

Objections and situations you will hear

“We never received the invoice.” Send it during the call and confirm the correct billing contact. If it has been going to an old address, that is a process problem worth fixing on the account.

“We are disputing the whole thing.” Route it to review and set a response deadline. Do not adjudicate a dispute on a payment call.

“Cash is tight this month.” Ask what date funds are available and take that date. A specific Friday beats a vague “next month.”

“We already paid that.” Ask for the payment date, method and amount, then check your records before calling again. Calling on a paid invoice damages the relationship more than the balance is worth.

“Take it off the account, we are leaving.” Follow your policy on account closure and final balances, and route it to whoever owns retention.

Dispositions

• Promise to pay with the date and amount.
• Paid with method and confirmation.
• Payment plan with the schedule and the written confirmation.
• Invoice disputed with the line item and the review deadline.
• Insurance pending with the payer and expected date.
• Hardship referral to the right internal workflow.
• Wrong contact and remove the record.
• Do not call on any stop request.

What the AI summary captures

DialBreeze records and transcribes connected calls. For AR work, keep the structured fields to account, contact, amount discussed, promise date, dispute detail and the documents requested. Do not let service or clinical detail land in a general-purpose note field. If the account involves medical services, the summary should mirror what your privacy review permits and nothing more. Verify the amount and date against the recording before the note drives a schedule change.

Compliance lines that matter

The FDCPA framework at 15 U.S.C. 1692a defines who counts as a debt collector, and Regulation F at 12 CFR 1006.2 and 12 CFR 1006.6 governs third-party conduct including calling times. TCPA restrictions at 47 CFR 64.1200 can reach wireless numbers regardless of who owns the debt, and many states have their own rules for medical debt, hospital billing and payment plans. Your written policy should state clearly which balances are called, what may be said on voicemail, and how disputes and hardship requests are documented. Recording rules vary and several states require all parties to consent, so disclose when you record. This page is not legal advice, and counsel should review the program before dialing begins.

Practice it before the real list

Run five sandbox calls where you verify identity before saying any amount, and five where the customer disputes half the invoice. The second set is where AR specialists argue instead of collecting, and the discipline of splitting the balance is what makes the block productive.