Send invoice reminders with AI-drafted follow-ups

Chasing overdue invoices is easy to postpone. Every week, an Orkeste agent lists the overdue invoices in Stripe or in your Airtable tracker and drafts a reminder for each: polite, specific, with the amount, the due date and the invoice number. Finance approves; from Outlook the email is sent, from Gmail it becomes a draft.

The problem

Reminders go out late and all with the same template. The tone is wrong for the customer who always pays, and right only for the one who never does.

How the workflow runs

Runs: Every week on the day you set.

  1. List overdue invoices: The agent lists open invoices past their due date in Stripe, or reads your Airtable tracker.
  2. Check recent emails: It reads recent emails with the customer, so it does not chase someone who already promised to pay.
  3. Draft: It writes the reminder with a tone set by how late the invoice is and the rules in its briefing.
  4. Approve: Each reminder waits in Validations for finance.
  5. Send or draft: Approved reminders are sent from Outlook or saved as Gmail drafts.
  6. Log: It updates the Airtable record with the reminder date.

Every reminder waits for finance's approval, and in Gmail finance still presses send.

Who does what

What this workflow does not do

Works with your stack

Questions about this workflow

Why does Gmail create a draft?

Gmail approvals create drafts by design, so a person sends the email. From Outlook, approved emails are sent directly.

Can it read our accounting software?

Not today. Use Stripe invoices or an Airtable table of open invoices as the source.

Can it adapt to the customer?

Yes. Describe in the briefing how to treat key accounts, first reminders and repeated delays.

Related workflows

Keep reading