Invoice & Payment Chaser
Slug: ai-invoice-payment-chaser · Category: Billing & Collections · Provisioning: Requires AgentLane staff approval
Escalates overdue-invoice follow-up in tone as the days pass, computing days overdue in code so the email never states a figure the AI invented. The first agent in the catalog that runs after the job is won and done — the point where small businesses quietly lose money because nobody enjoys making the call.
Required credentials
| Provider | Used for |
|---|---|
anthropic | Writes the chase email at the escalation level the code step decided |
resend | Sends it |
customjs | Not a stored credential — a step-capability flag for the inline overdue calculation. Doesn’t block provisioning on its own. |
Industry fit
Home Services, Construction, Solar, Automotive, Accounting, Legal, Insurance, Dental, Veterinary, Healthcare, Recruitment — verticals that invoice after the work and then wait to be paid. Not the ones that take payment at the point of sale.
How to deploy
Request it the same way as any non-instant agent — see Deploy your first agent. Post each overdue invoice to its webhook with clientId, customerEmail, invoiceNumber, amountDue, dueDate and a paymentLink.
Flow
Webhook (overdue invoice) ──► Look up client config ──► Classify overdue (code) ──► Draft chase (Claude) ──► Send email (Resend)The classify step is the guardrail, not a formality. It refuses to run on an unparseable due date, a non-positive amount, or an invoice that isn’t actually overdue yet, and it — not the model — decides the tone: friendly first reminder under 8 days, firm follow-up under 30, final notice beyond that. The drafting prompt is only allowed to restate the figures it was handed, never to invent late fees, interest or legal threats.