High-regulation notice
This is a C fit. First-party accounts receivable looks simpler than third-party collection, and often is, but the rules turn on facts a dialer cannot check: who owns the debt, whether it was in default when obtained, whether it is medical, and whether the account will be referred to a third-party collector. Medical billing and medical debt carry additional state rules and privacy considerations. Nothing here is legal advice.
Before the first block, decide in writing which balances may be called, what may be said on a voicemail, who may be contacted, and when an account leaves first-party handling. Route that through counsel and your compliance lead.
What this page actually covers
For AR that means the conversations are real, the promises are documented and the disputes are routed, rather than an automated reminder going to a phone nobody answers.
The defensible use is calling your own customers about your own invoices, with identity confirmation, no account detail on voicemail, and a suppression list that holds across every queue.
Three workflows an AR team runs
Past-due invoice follow-up. The aging export is the queue. The call confirms receipt, finds out why it is unpaid, and offers the terms the company approved. Business contacts are reached during business hours.
Payment-plan and promise-to-pay follow-up. The highest-yield list in the department, because the customer already agreed to something. The call is short and specific: the date, the amount and the method.
Medical balance calls. A separate queue, a separate script and a separate policy. Several states restrict medical debt collection and hospital billing practices, and medical information can carry privacy obligations, so it should never run on the general commercial list.
What the record should carry
The contact reached, the promise date, the dispute or hardship request, insurance status, and a permanent do-not-call flag. If a call reaches someone other than the responsible contact, end it and log it rather than discussing the balance; the CFPB’s Regulation F official interpretation on third-party communication in 12 CFR 1006.6 explains why that discipline matters, and the same principle applies as a matter of ordinary data hygiene even when FDCPA does not cover the account.
The rules, stated specifically
FDCPA section 803(6)(F), 15 U.S.C. 1692a(6)(F), excludes from the definition of debt collector a person collecting a debt originated by that person that was not in default when obtained. That exclusion is detailed and fact-specific, and it stops applying if the debt is referred to a third-party collector. The CFPB’s Regulation F definition in 12 CFR 1006.2 and its official interpretation address what counts as conveying information about a debt, which is why voicemail content matters.
On the calling side, 47 CFR 64.1200(a)(1) restricts autodialed and prerecorded calls to wireless numbers, calling hours for telephone solicitations are the legal calling window in the called party’s local time, and state recording consent rules vary.
Why publish this page at all
AR teams search for a collections dialer and often get pointed at tools built for third-party agencies, which is the wrong control set. This page states the distinction: first-party handling has fewer federal collection duties but the same need for identity discipline, suppression and medical-debt care.
What you need to start
- A written policy covering scope, voicemail content, medical balances and referral triggers.
- Counsel review for your state and your industry.
- Prepaid calling credit: DialBreeze provides the calling and the numbers, at $0.75 per dialing hour.
- An aging export and a disposition set that maps to your accounting system.
Pick your plan and seats, check out, set your password. Load calling credit and start dialing.; rehearse the script with test data before live accounts are called.
Medical balances justify their own queue
A hospital or clinic billing office has two kinds of receivables, and they behave nothing alike. Commercial invoices get paid when the customer decides to pay. Patient balances depend on insurance processing, deductible status, charity care eligibility and, increasingly, state law.
Several states restrict medical debt collection practices, hospital billing timelines and credit reporting of medical debt. Some require financial assistance screening before certain collection steps. That is why medical balances need a separate queue, a separate script and a separate escalation path, and why running them through the same reminder cadence as commercial invoices is a mistake.
A promise to pay needs a date and an owner
The classic AR failure is a promise recorded as a mood rather than a fact. “Customer says they will pay” is not actionable. A promise with a date, an amount, a method and the name of the person who committed is.
That is what the disposition set is for. A promise-to-pay call should produce a specific follow-up date, and the follow-up block should contain only accounts whose date has passed. When the queue is built that way, the specialist is not re-calling people who already did what they said they would, which is the fastest way to sour a paying customer.
Business contacts and consumer contacts
A vendor invoice to a company is a business conversation, and calling hours analysis differs from a consumer debt call. In practice the discipline is the same: reach the accounts payable contact during business hours, end the call immediately if you reach someone else, and never discuss a balance with a person whose relationship to the account you cannot establish.
That last rule is worth enforcing even where FDCPA does not reach, because a first-party call that discloses a balance to the wrong person in the company can damage the customer relationship and, in some industries, create a privacy problem.