Not on its own authority. An AI agent can run every pre-placement check, build the file and draft the customer notice, which is most of the work. The decision to pass the debt on, and with it the customer's data and the relationship, belongs to a named person, who approves each placement or each batch the agent has prepared.
Why is placement a decision with weight?
Passing a debt to a collection agency changes three things at once. The customer's personal data goes to another company. A different organisation starts contacting them, often with less context about their situation. And the lender's relationship with the customer moves into a harder phase that is difficult to reverse; recalling a debt from an agency is possible but the customer has already received the letters.
Mistakes here are painful. A debt placed while the customer is on an agreed payment plan, while a complaint is open, after the customer has died, or when the balance is wrong will cause distress and complaints, and may breach the lender's duties. In many markets, debts also become harder or impossible to enforce after a limitation period, and pursuing them anyway can be unfair. Every one of those is a check the agent can run. None is a check it should waive.
What must be true before any debt is placed?
- the account is in default under the lender's policy and the required notices were sent;
- the balance has been reconciled, including fees, interest and payments in flight;
- there is no open dispute, complaint, or payment arrangement;
- the customer is not flagged as vulnerable, in insolvency, or deceased;
- the debt is within any limitation period that applies;
- the agency is on the lender's approved list and the contract covers this type of debt;
- the customer has been told, in approved wording, that the debt may be passed on.
What may the agent do, and what stays with a person?
| Step | The agent | Stays with a person |
|---|---|---|
| Selecting candidate accounts | Applies the placement criteria, depth 1 | Changing the criteria |
| Running pre-placement checks | Runs each and records the result | Accounts where any check is unclear |
| Reconciling the balance | Compares ledger, payments and charges | Correcting errors |
| Drafting the notice to the customer | Drafts from the approved library, depth 2 | Approving the wording |
| Preparing the placement file | Assembles only the data the contract needs | Approving the data shared |
| Placing the debt | Never on its own | A named person approves each placement or batch |
| Recalling a placed debt | Prepares the recall when new facts arrive | Approving it |
Sending data and the customer relationship to a third party without approval is a textbook case of excessive agency: an agent with the power to do something far beyond what its job needs.
An example: a batch of forty
Take a lender preparing its monthly placement batch. The agent selects forty defaulted accounts that meet the criteria and runs the checks.
Thirty-four pass every check. Three have open complaints logged in the complaints system, not the collections system; the agent removes them. One has a bereavement notice received two days earlier. One has a balance that does not reconcile because a payment of 200 is still being processed. And one has had no payment or acknowledgement for long enough that a limitation period may apply.
The agent sends the batch of thirty-four to the collections manager with the six exclusions listed and reasons for each. The manager approves the thirty-four, sends the bereavement case to the specialist team, and asks the legal team about the limitation question. Nothing leaves the lender until the manager signs.
What controls make it safe?
- Checks across systems. The agent reads complaints, bereavement and arrangement records, not just the collections ledger.
- Data minimisation. The placement file includes only what the agency contract requires.
- Batch approval by a named person. The approval is filed with the list, the exclusions and the reasons.
- A pass floor on the checks. Certification requires the agent to catch every exclusion in the test set; a single miss fails the gate. See how to set the pass floor for each certification gate and what score an AI agent should need to pass.
- Recall on new facts. A complaint or difficulty flag raised after placement triggers a recall case.
Placement often follows failed attempts to agree terms; see whether an AI agent can negotiate a settlement on a debt and handling debt dispute claims with an AI agent. The general limits are in AI agents in banking: what they may and may not do.
Questions people ask
Is selling a debt different from placing it with an agency?
Yes. Selling transfers ownership of the debt to the buyer; placing keeps ownership with the lender and uses the agency as a service provider. Both need a person's approval, and a sale usually needs more.
Can the agent tell the customer which agency will contact them?
Yes, in the approved notice, once the placement is approved. Naming the agency before approval risks telling the customer something that may not happen.
What happens if the customer calls the lender after placement?
The agent can see the placement and explain who is handling the account. If the customer raises a dispute or difficulty, the agent opens a case that can lead to a recall.