2 Collections AI Agents, Live in Production.
2 live agents automate collections within billing. They all run on a schedule. Each one publishes the inputs it needs, the steps it works through and what it hands back.
-
Dunning Management
Place every overdue account at the right stage of the dunning sequence, set the next action and date, and hand the escalations to a person. No customer contact is drafted here.
-
Overdue Invoice Chasers
Draft a collection note for each overdue invoice, pitched to how late it is. Every draft is approved individually — nothing is sent.
Automating the sequence, approving every message individually
Collections automation fails in a specific and damaging way. A dunning sequence is easy to implement and, once running, it escalates on a schedule without reading the account. So a customer who is disputing an invoice for a good reason receives a firm demand, a customer whose payment crossed in the post receives a final notice, and a long-standing account gets a legal threat generated by a rule. Each of those costs more than the invoice. The opposite failure is manual collections, where the sequence depends on whoever has time — accounts drift, nobody knows which stage anything is at, and the oldest debt gets chased hardest regardless of whether it is recoverable.
These two agents split the sequencing from the contact, which is the design decision that makes automated collections safe. Dunning Management places every overdue account at the right stage, sets the next action and date, and hands the escalations to a person — and deliberately drafts no customer contact at all. It manages state, not communication. Overdue Invoice Chasers then drafts a collection note for each overdue invoice, pitched to how late it is, with every draft approved individually and nothing sent. Approval per note rather than per batch is what catches the account where the tone would be wrong: the reviewer sees this customer, this invoice, this wording, and can stop the one message that should not go.
What this moves
- Accounts at the correct dunning stage
- Every overdue account is placed at the right stage with a next action and date, so the sequence advances by rule rather than by whoever had time.
- Firm demands sent to the wrong account
- Collection notes are drafted and approved one at a time, so a customer with a legitimate dispute or a payment in transit does not receive an escalation.
- Escalations reaching a person
- The accounts that need judgement are handed to someone rather than escalated automatically to the next template.
Billing
How AI agents handle collections
Drawn from the 2 agents above — what they require, how they run, and what comes back.
What they need
- Overdue invoices
- Dunning policy
- Chaser settings
What comes back
- The sequence
- Dunning plan
- Needs a decision
- Escalation handover
- Handover to collections
- Collection summary
- Drafted chasers — approve each individually
How they run
- Runs on a schedule
- 2
- Steps per run
- 2–3
- Credits per run
- 6
Where collections fits in billing
Collections slip because chasing is manual and nobody owns it end to end. Agents run the follow-up on schedule, which shortens the gap between invoicing and payment without anyone having to remember.
Next Step
Deploying collections agents
These run as-is against the inputs listed above. Most deployments adapt one — a different source system, a different tolerance, a different approval path. The first call establishes which.