← All articles

Invoicing

How to Automate Invoice Reminders With AI (and Actually Get Paid)

The Ootto Team · 3 min read · June 10, 2026

1Claude Code

Type this. The free Claude content skills land in your skills folder.

Prompt

git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git && bash claude-content-skills/install.sh

Copies all fourteen into ~/.claude/skills. Restart Claude and every one of them is available.

2Claude AI or Cowork

No shell in these, so there's nothing to clone - sign in and add the connector instead, and get the same free Claude content skills running against a real account.

Ootto

Your 24/7 Instagram Growth Operator

Skip the manual setup

  • Finds winning content opportunities
  • Creates on-brand Reels and captions
  • Replies to comments instantly
  • Starts personalized DM conversations
  • Qualifies leads automatically
  • Runs up to 50 Instagram accounts
  • Helps book calls and drive sales
  • Learns and improves with every interaction

One AI. Every Post. Every Comment. More Leads. More Sales.

Sign in

Made by Ootto

Real reels, rendered by the engine

Six demonstration brands, six finished reels - the same engine that studies a niche and builds the reel actually made these, start to finish. No shot lists, no editors.

Chasing unpaid invoices is the work nobody starts a business to do. It's awkward, it's easy to forget, and the longer you wait, the harder it gets to collect. The fix isn't working harder on follow-ups — it's removing yourself from them. Here's a simple cadence that works, and how to put it on autopilot with AI.

Why invoices go unpaid (it's usually not the money)

Most late payments aren't refusals — they're drift. The invoice lands in a busy inbox, gets mentally filed under "later," and nothing reminds the client until you do. The businesses that get paid fastest aren't more aggressive; they're more consistent. They follow up on a schedule, every time, without it depending on someone remembering.

That consistency is exactly what's hard to do by hand and easy to automate.

The reminder cadence that works

You don't need a complicated dunning system. A three-touch cadence, anchored to the due date, covers the vast majority of cases:

1. The polite nudge (0–7 days after due)

Friendly, assumes good faith. People miss dates; this is a gentle reminder, not an accusation.

Hi [Name] — just a quick note that invoice [#] for [amount] was due on [date]. If it's already on its way, thank you! If not, here's the link to pay: [link].

2. The firm reminder (8–21 days)

Direct, still professional. State the overdue amount and make paying effortless.

Hi [Name] — invoice [#] for [amount] is now [X] days overdue. Could you let me know when we can expect payment? You can pay here: [link].

3. The final notice (22+ days)

Clear about next steps, without burning the relationship.

Hi [Name] — invoice [#] remains unpaid [X] days past due. Please arrange payment by [date] to avoid [late fee / pause in work]. Pay now: [link].

Three templates, triggered at roughly +7, +14, and +21 days past due, will resolve most late invoices before they become real problems.

Where AI changes the game

A cadence is only useful if it actually runs. This is where doing it manually breaks down — and where AI earns its place:

  • It triggers on time, every time. Reminders fire on the due-date schedule without you tracking who owes what.
  • It writes in your voice. Instead of robotic templates, AI drafts each reminder to match how you talk to clients — warmer for long-standing customers, firmer for chronic late payers.
  • It reads the replies. When a client responds, AI can classify it — "paid," "will pay on [date]," "disputing" — and route the ones that actually need you, while handling the routine acknowledgements itself.
  • It stops when paid. Connected to your payment tool, it knows when an invoice clears and cancels the remaining reminders automatically — no awkward "please pay" after they already did.

The result is the consistency of a collections process without the cost or the discomfort of running one.

How to set it up

You've got two broad options:

  1. Build it yourself with a workflow tool (Zapier, Make, n8n) — connect your invoicing app, write the templates, set the delays, and maintain it. Workable if you like building. See our Zapier alternatives guide for the options.
  2. Let an autopilot handle it. Ootto connects to your email and payment tools, learns your tone, and runs invoice follow-up as one of its built-in jobs — drafting reminders, reading replies, and stopping when an invoice is paid. Nothing to build.

If you already enjoy maintaining automations, option 1 is fine. If invoice-chasing is exactly the kind of work you want gone, option 2 removes you from it entirely.

The bottom line

Late payments are rarely a pricing or product problem — they're a follow-up problem. A consistent three-touch cadence fixes most of it, and AI makes that cadence run without your attention. Set it up once, and "chasing invoices" stops being a thing you do.

Route A: do it yourself

Start with the exact free skill for this outcome

MIT, no account, no email. Install first, then run the command for your account.

For chasing overdue invoices: Invoice Chaser

Prompt

git clone --depth 1 https://github.com/Ootto-AI/claude-invoice-skills.git && bash claude-invoice-skills/install.sh

Installs the free MIT Invoice Skills bundle into ~/.claude/skills in one shot.

Prompt

/invoice-chaser [invoice number, amount, due date, days overdue]

Drafts the right payment reminder, tone matched to how late the invoice is.

Route B: let Ootto run it

Ootto replicates this on autopilot

Open the dashboard, connect once, then let the pipeline handle research, production, and lead replies.

1Sign in

Open the connector dashboard

Go to /content/login, sign in, and open your Ootto content dashboard.

Ootto content dashboard landing screen after sign in
2Connect

Add Ootto to Claude

Use the one-button Add flow so Ootto appears in Claude's Connectors panel.

The connector card with Add Ootto to Claude button
3Verify

Claude shows the connector

The connector lands in Claude's Connectors settings, confirming Ootto is wired.

Claude Connectors screen showing Ootto connector setup
4Auto onboarding

Board reads back your context

Your audience, pillars, voice, and creator signals are filled from account context.

Dashboard board-ready state with audience, voice, and niche fields
5Research

What is actually working now

Ootto pulls what is moving in your niche and loads ranked examples in board.

Idea Studio showing niche winners and ranked creator reels
6Loop

Reel + comment-to-DM lead loop

Reels move to ready state and comments are answered with public replies plus DM follow-ups.

Unattended reel pipeline with production and lead capture continuing overnight
Sign in

Ootto

Run Ootto in your Claude

Skip the manual setup

  • Finds winning content opportunities
  • Creates on-brand Reels and captions
  • Replies to comments instantly
  • Starts personalized DM conversations
  • Qualifies leads automatically
  • Helps book calls and drive sales
  • Learns and improves with every interaction

One AI. Every Post. Every Comment. More Leads. More Sales.

Start free trial

$1 now, automatically refunded, for a 7-day trial - then $49/mo. Cancel anytime.

Get started

Let Ootto run it for you on autopilot

Sign in

Let Ootto hyper-power your Instagram growth.

Sign in

Keep reading

Content

14 Claude skills for Instagram growth from post to lead

Fourteen free, MIT-licensed Claude skills that help you create Instagram content that stops the scroll, gets posted, and converts comments into leads.

Jayant Joshi · 7 min read

Content

3 Claude skills for turning Instagram reach into customers

2,000 visitors came in from faceless Instagram reels, but traffic was not the win: the free MIT repos + automated system that build, post, and audit those reels, then turn comments into DM leads and leads into customers.

Jayant Joshi · 4 min read

Content

I gave Claude my Instagram and it started an auto-reply system

A real run with 78 posts found, 560 comments classified, and 10 confirmed replies after fixing two production failures.

Jayant Joshi · 4 min read