Collections handled
without burning the relationship.
Chasing overdue invoices is the work nobody wants. Send it too cold and the customer churns; send it too late and the cash never comes. A Loomal collections agent runs the dunning sequence with the right tone, the right cadence, and the right escalation — from a real finance identity, fully audited.
API Primitives used
mail.sendRun the dunning sequence
Reminders go from a real finance identity at the right cadence. Tone steps up gradually so the customer is informed, not blindsided.
vault.getPull invoice and payment data
Open invoices, payment history, and customer terms live in the vault for the agent to read per outreach.
mail.list_messagesCatch responses and excuses
Replies get classified as paying, disputing, or going dark. Each path gets the right next action.
Collections kills accounts you spent years winning.
AR teams send the same dunning sequence every cycle. The first message is friendly, the second is firm, the third is final. Each one is a chance to either recover the cash or burn the relationship — and humans inevitably get the tone wrong because the work is repetitive and demoralizing.
An agent doesn't get tired or testy. It runs the sequence with consistent tone, escalates only when policy says, and routes the genuinely stuck accounts to a human early — protecting both the cash and the customer.
How to build it.
vault.getRead the AR ledger
Agent pulls overdue invoices and customer payment history from the vault on every collection cycle.
mail.sendSend the right touch
Each customer gets the next message in the dunning sequence — 7, 14, 30, 60 day touches with escalating but professional tone.
mail.list_messagesHandle the reply
Payments get acknowledged, disputes get routed, and silent accounts get the next step in the sequence — automatically.
Example prompt
“For every invoice over 30 days late, send a friendly reminder from my finance agent address. For invoices over 60 days, escalate to a payment-plan offer. Notify me on any dispute reply.”
What AR teams build.
Standard dunning
Agent runs the company's dunning policy across the entire AR ledger every day, with consistent tone and timing.
Payment-plan offers
For accounts over 60 days, agent offers a structured payment plan and books a call with the AR lead.
Dispute handling
When a customer disputes, the agent collects the details and routes them to the AR lead with full context.
Multi-currency collections
International invoices get currency-aware messaging and local payment instructions.
Customer-tier escalation
Strategic accounts get a softer sequence and earlier human handoff than transactional ones.
Why collections needs a real identity.
AR communications carry legal weight in many jurisdictions. They have to come from a verifiable source, with a clear audit trail, in a defined sequence. Sending dunning messages from a generic outbound tool creates compliance exposure; sending them from a personal address creates relationship risk.
Loomal gives AR its own identity — verifiable sender, encrypted invoice data, audited per touch. Collections runs at machine consistency without losing the human-grade tone or the legal defensibility.
AR data encrypted
Invoices and payment history live in vault entries scoped to the finance identity.
Per-touch audit
Every dunning message is logged with timestamp and the AR lead who authorized the policy.
Compliance-grade trail
DKIM headers and audit logs provide the defensible record collections work requires.
Recover cash without burning customers.
Dunning, escalation, and disputes in one autonomous loop.