Sweeps QuickBooks every morning, groups what is overdue by customer, and leaves one reminder email per customer in your Gmail drafts with a Slack summary of where the money is.
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Overdue sweep 12 August
Nine invoices are past due for a total of 38,420.00 GBP. Meridian Property Group holds three of them between 12 and 19 days old for 14,900.00 GBP, Calder Fit Out has a single invoice at 6 days for 2,180.00 GBP, and the remaining five are one invoice each between 3 and 11 days old. Nobody has been emailed about any of them this week.
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect QuickBooks
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Gmail
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Dunning policy
Your reminder ladder for overdue invoices - how many days past due before the first nudge, how the tone hardens at each step after that, the smallest balance worth chasing, how long to wait between reminders, and which accounts (payment plans, live disputes, your biggest customers) never get a templated email.
Choose which agent runs it
NoClick's built-in models work out of the box — or bring Claude Code, Codex, and other coding agents on your own subscription.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Most small businesses are owed more than they think, and the reason nobody chases it is that writing the fifth polite reminder of the week is miserable work. This agent reads your QuickBooks ledger every morning, groups the overdue balances by customer, and leaves a reminder in your Gmail drafts pitched at the age of their oldest invoice, plus one Slack line showing the aging across the whole book. It never sends and never posts to the books, so the awkward calls and the accounting both stay with you.
What do I need connected before it runs?
A QuickBooks Online connection, a Gmail account to hold the drafts, and the Slack channel you want the morning summary in. Then you write your dunning policy in plain English: the days, the tone at each step, the minimum balance, and who is off limits. The staged test runs let you read the drafts it produces before a real invoice is involved.
Could it chase somebody who has already paid?
It reads the balance due at the moment it runs, so an invoice settled yesterday is not in the sweep, and it skips a customer whose books show a payment posted since the invoice went out. The real protection is that nothing leaves your account on its own: a draft that turns out to be wrong is a draft you delete. Payments logged after the 9am sweep are the one gap, and reading the drafts before sending closes it.
What does it cost to run?
One run each morning, so around thirty a month whether you have four overdue invoices or four hundred. The run is a couple of QuickBooks reads, one draft per overdue customer, and one Slack message, so it stays short. Its QuickBooks connection is used for reading and drafting only, which means the cost of a mistake is a draft nobody sends.
Free to start. Guided setup, a test run against staged conversations, and it's live.