First-party vs. third-party collections: where AI fits

The line between first-party and third-party collections changes which rules bind you — and where an AI voice agent is safe to deploy. Here’s how to keep the software on the right side of “principal purpose.”

First-party and third-party collections sit under different regulatory weights, and that difference shapes where an AI voice agent belongs and how it must be operated. Get the distinction wrong and you can turn a compliant tool into an unlicensed collector. The safe pattern is the same in both settings, but the reasons it matters shift with who owns the debt.

The distinction in plain terms

First-party collections is a creditor working its own accounts, often early and in its own name. Third-party collections is a separate agency or debt buyer pursuing debts owed to someone else, squarely within the FDCPA and state licensing regimes. Many Reg F expectations — disclosure, honesty, frequency discipline — are good practice in both, but third-party work carries the fuller federal-and-state licensing load.

Where AI fits in each

In both settings, the AI voice agent should be software operated by the party that holds the license or the right to collect — a creditor working first-party accounts, or a licensed agency working third-party ones. What the agent does is similar: disclose that it is AI, confirm the right party, deliver required notices, record with consent, and hand off to a human when needed. What changes is which body of rules you are proving compliance against.

The trap: becoming the collector yourself

The line to guard is “principal purpose.” If a technology vendor’s own agents place calls and pursue debts, that vendor risks being treated as a debt collector whose principal purpose is collection, dragging it under the FDCPA and state licensing such as California’s DCLA. The way to stay clear is structural: sell software to a licensed collector; never let the vendor’s own agents be the collector.

• First-party: the creditor operates the agent on its own accounts, in its own name.
• Third-party: the licensed agency operates the agent under its license.
• Either way: the vendor supplies software, not a collection service.
• Never: the vendor’s agents originate and pursue the debt themselves.

Operate it as a tool, not a service

Teltura is built to be operated by the collector, not to become one. The console is built for the operator rather than the engineer, edits are self-serve — “No ticket. Ever.” — and the agent discloses it is AI, records with consent, and keeps a compliance ledger across channels. That keeps control, and the compliance obligation, with the licensed party where it belongs.

Whether you are first-party or third-party, deploy the AI as software you operate under your own authority. The moment the vendor’s agents become the collector, you have changed which rules apply — keep the tool a tool.