How the AI chasing agent drafts an overdue-invoice follow-up
The AI chasing agent reads the overdue invoice from the same ledger that drives AP and AR, drafts a tone-appropriate follow-up in your house style, and hands it back for a human to review, edit, and approve before it ever goes out. Below is a worked example on a sample Net-30 invoice — read on the left, draft on the right.
- Client
- Northwind Logistics
- Invoice #
- INV-2026-0419
- Amount
- $12,480.00 USD
- Due date
- 2026-07-02
- Days overdue
- 32
- Last contact
- 2026-07-21
- Contact email
- [email protected]
Sample draft — generated by the AI chasing agent for illustrative purposes. In production, the agent tailors tone, length, and next-step asks to your segment presets and the customer's prior reply history.
The AI never sends on its own. Every drafted message lands in your team's review queue alongside the originating invoice, the full payment history, and any prior chase or dispute context — so the human who picks it up does not have to re-stitch anything from an inbox.
Edit the copy in place, swap the tone, or change the next-step ask. Approve to send, or route the thread to a controller if the invoice hits a configured dollar or aging threshold. Once you sign off, the agent takes it from here — pauses the moment the customer replies, and resumes only after a reason-coded sign-off.
Every status change, edit, and approval is reason-coded in the audit trail, so the same draft is auditable end-to-end the first time and faster to clear the second time a repeat reason shows up on the same account.
See it run on your real overdue invoices
The worked example above is illustrative. The real agent reads from your ledger, drafts in your house style, and hands each follow-up to your AR team for a human pass before it goes out.