Grant the agent collections permissions action by action. It may read arrears, log notes and send reminders within your contact rules at depth 3, record promises and set up plans inside your limits, and add protective flags such as vulnerability or a breathing space. It may never remove those flags, issue defaults, refer debts onward or write off balances.
What does the connection involve, and who owns it?
A collections system tracks accounts in arrears and everything done about them: contacts, promises, plans, fees, notices, referrals. Connected to an agent, it lets customers in difficulty get answers and arrangements quickly. It also hands the agent the means to contact people who may be stressed or vulnerable, at volume, with consequences that cannot be taken back.
The head of collections approves each capability. Compliance owns the contact rules and protective flags. The integration team builds the connection. For where collections sits among banking uses of agents, see our guide to AI agents in banking.
Which permissions should you grant, and at what depth?
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Read account and arrears | Balance, history, flags, previous contacts | 1 | Nothing |
| Log contact notes | Records what was said and agreed | 3 | Nothing |
| Send reminders | Messages inside the contact strategy | 3 | Any message outside the approved templates |
| Record a promise to pay | Logs date and amount the customer gave | 3 | Promises outside policy limits |
| Set up a repayment plan | Creates a plan inside the limits matrix | 3, or held | Plans outside the matrix, any concession |
| Add a protective flag | Marks vulnerability, breathing space, dispute | 3 | Nothing; adding is always allowed |
| Remove a protective flag | Not available | refused | Named collections specialist only |
| Apply fees or charges | Not available | refused | Policy decision by a person |
| Issue default notice, refer onward, write off | Prepares the case | 2, held | Named decision-maker in every case |
Plan setup is covered in its own playbook: letting an AI agent set up payment plans in your collections system.
How do you connect it, step by step?
- Person, head of collections: approves the capability list above, adjusted to your products. Evidence: approved list with depths.
- Person, compliance: loads the contact strategy as bounds. Channels, times of day, frequency per week, approved templates per arrears stage. The collections contact strategy matrix gives a structure. Evidence: contact rules as versioned configuration.
- Integration team: builds one route per capability. Adding a flag and removing a flag are separate routes, and only one is granted. Evidence: route list.
- Integration team: gives the agent its own identity with grants matching the approved list. Evidence: grants export.
- Platform, on each call: checks bounds. Contact limits use running counts for the customer across all channels and all senders, people included. Evidence: verdict with counts.
- Agent, at its certified depth: works cases. Every action carries the case reference and the facts used. Evidence: actions linked to case.
- Person, named specialist: decides held items. Evidence: decisions and reasons.
- Integration team: wires revocation per capability and for the whole connection. Evidence: drill results.
Which controls matter, and what is recorded?
Protective flags are one-way for the agent. It can add a vulnerability, dispute or breathing space flag the moment it sees a reason. It cannot remove one. Evidence: refused verdicts on removal attempts.
Flags stop contact automatically. Once a protective flag is set, reminders stop until a person reviews. Evidence: suppressed contacts logged.
Contact counts include people. An agent that sends its weekly limit on top of what the human team sent breaches the strategy. Evidence: per-customer running totals.
Difficulty before money. The agent must screen for signs of financial difficulty before asking for payment; the argument is made in collections agents must spot difficulty before they ask for money. Evidence: screening result on each contact.
Irreversible steps held. Default notices, credit reporting changes, agency referrals and write-offs have effects that outlast any correction. Why these sit apart is explained in irreversibility in collections. Evidence: held verdicts with the decision-maker.
Full log. Every read, note, message, promise, plan and flag, with agent identity and verdict. Evidence: the record.
What should you measure?
- Contacts per customer per week, against the strategy's limit.
- Protective flags added by the agent, and how many a person later confirmed.
- Promises kept and plans kept, against cases handled by people.
- Complaints about contact, frequency or tone.
- Held items by type and time to decision.
Where does it usually go wrong?
The agent inherits a dialler's rights. It connects through an account built for automated reminders and can send at volumes no person would.
Templates drift. The agent personalises messages beyond the approved wording, and a reminder starts to read like a threat. Hold anything outside the templates.
Flags are removed to "unblock" a case. A team frustrated with suppressed contact asks for the agent to clear flags. The refusal is the control working.
Contact rules are checked per channel. Three texts, two emails and a call each stay under their own limit and together overwhelm the customer.
Revocation is untested. When a template or contact rule goes wrong, you need to stop reminders within minutes without stopping note-taking or flagging. Practise switching off one capability alone before you need to.
Collections is treated like order handling. A connection designed for order changes, such as the one in connecting an agent to your order management system, lacks the protective flags and contact rules collections needs.
Questions people ask
Can the agent call customers in arrears?
If your contact strategy allows automated calls, at the approved times and frequency, and the agent says it is automated. Many firms start with messages and add calls later.
Can the agent accept a payment during a contact?
It can direct the customer to your payment channel. Taking card details inside the conversation brings the agent into card data scope and is better avoided.
What happens when a customer disputes the debt?
The agent adds a dispute flag, stops collection activity on that balance, and opens a dispute case for a person. It does not argue the merits.