A 21-day overdue invoice follow-up, drafted by Nora
Quick answer
Overdue invoice follow-up works when each reminder reflects what the customer has already said and paid. In Omni Studio, Nora reads the invoice, job notes, and history, then drafts the reminder with a Stripe invoice link and a payment-plan option. Sending and the plan wait for the owner.
Overdue invoice follow-up works best when each reminder is specific, polite, and easy to act on. The hard part is knowing what this customer has already said and done. AI employee Nora reads the invoice and the thread, drafts the reminder, and waits for the owner's approval before anything sends.
We set up the workflow described here with you during Custom Build or Enterprise setup. We agree on the records, tool connections, and approval rules before you use it. Custom workflows are not included in the Pilot. Ask our team to configure this example before you try it. The free 14-day workspace uses sample data with simulated calls, texts, and email; daily limits apply. Phone numbers and message delivery on paid plans use your own Twilio account, billed separately by Twilio.
Illustration with sample data. This is a walk-through with sample data. The business, the people, and the numbers are made up to show how the job works in Omni Studio. It isn't a customer story.
This invoice is 21 days past due at a fictional company, Hollowbrook Landscaping. Dev is the owner, and Priscilla is the customer. Nora, the AI employee for billing, did the reading and drafting. A five-step cadence follows.
What came in?
On Monday, October 12, at 8 a.m., Nora's weekly list of open invoices showed one 21 days past due. Nora logged it as a record card:
| Field | Sample value |
|---|---|
| Invoice | 1042, to Priscilla, 18 Alder Row |
| Job | Spring cleanup, mulch, edging, and shrub trim, done September 7 |
| Amount | Full balance open, due Monday, September 21 |
| Reminders so far | Day 7 (September 28) and day 14 (October 5) |
| Books | Open in QuickBooks, no payment recorded |
What did Nora read before drafting?
| Record | What it said |
|---|---|
| Invoice and Stripe link | Four lines on one balance. The sample invoice link is still live and is set to expire October 21 |
| Job notes | Crew finished September 7. Priscilla signed off |
| Payment history | Two earlier invoices, paid on day 3 and day 5 |
| Last message | On October 6: "Sorry, I was traveling. Could I split this in two? Home on the 14th." |
A customer who paid fast twice and wrote back isn't a collections case. The reminder should answer her question.
What did Nora draft?
To Priscilla, from Dev's inbox
The reminder email
- Thanks her for the October 6 reply
- States the due date once
- Includes the invoice's Stripe link
- Offers one payment or two
Not in the draft
Left out on purpose
- A late fee not in the signed terms
- Any threat or collections wording
- A scolding tone
- Any change to the invoice
In this sample, the invoice link expires October 21. Nora includes that date in the draft so Dev can check it.
The sample plan is two equal payments. Dev checks how to collect each payment before approving the offer.
What waited for the owner, and why?
Two things waited: the send, which is a message in the business's name, and the payment plan, which is a money term. In Omni Studio, sending, spending, signing, and changing records wait for approval by default.
Dev saw the draft and the reasons at 8:06 a.m. and could approve, edit, or decline.
He moved the second payment date from November 2 to October 30, and the edit is logged. Your approval rules are agreed during setup.
What happened after approval?
The reminder went from Dev's own Gmail inbox. In this example, Priscilla paid the first half on Thursday, October 15. Nora matched it to invoice 1042 and drafted the QuickBooks entry.
| Time | Action | Approved by |
|---|---|---|
| 8:04 a.m., Oct. 12 | Reminder and two-payment offer drafted | Waiting |
| 8:11 a.m., Oct. 12 | Reminder sent with Dev's date edit | Dev |
| 9:00 a.m., Oct. 15 | First half recorded in QuickBooks. October 30 reminder drafted | Dev |
Changing the books is a record change, so Nora drafted the entry and waited.
What if the customer disputes one line item?
On the 14th, before paying, Priscilla wrote: "The edging and haul-away line seems high. I think they only did the front beds." Nora did not argue or send the next reminder.
Nora pulled the evidence for that line only. The records disagreed, so the card for Dev shows both sides and his options. It doesn't pick a winner.
| Source | What it shows |
|---|---|
| Invoice, line 3 | Edging and haul-away, billed for front and back |
| Original quote | Edging listed for front and back beds |
| Crew notes | Front beds edged; back beds not done; debris hauled away |
Sample data: the four lines of invoice 1042 by status
- Lines not in dispute 3 lines
- Line under review 1 line
- Invoice 4 lines
3 lines + 1 line = 4 lines
Dev could keep the line, credit part of it, or call Priscilla. A credit changes the invoice, so it waited for him. The draft reply said the line was being checked.
Ask your lawyer which collection rules apply to your business. This is general information and does not replace a lawyer.
What is a simple overdue invoice follow-up cadence?
- Before it is due Send the invoice with a clear link and a due date.
- Day 1 to 7 A short, friendly reminder with the link.
- Day 14 A reminder that reflects what you know about the customer.
- Day 21 A personal note with options, such as two payments.
- Day 30 and later The owner decides: a call, a hold, or a firmer step.
How do you try overdue invoice follow-up on sample data?
The invoice follow-up use case runs this job on sample data. Nora is one of the seven AI employees. During setup, we connect your QuickBooks, Gmail and Stripe accounts for invoice records, reminder drafts and invoice links.
Also see landscaping quotes and routes, accounts receivable follow-up, and customer follow-up for contractors. We help import invoices kept elsewhere from a CSV file.
Frequently asked questions
How do you write an overdue invoice reminder email?
Keep it short. Thank the customer for any reply, state the balance and due date once, add the invoice link, and offer two payments. Leave out threats and fees not in your signed terms.
Can an AI employee send overdue invoice reminders on its own?
In Omni Studio, only with your approval. Nora reads the records and drafts the reminder and any plan. Sending and the plan wait for your approval, and every decision is logged.
What if the customer disputes part of an invoice?
Have the owner review the dispute and decide which reminders to pause. Show the owner the quote, crew notes and invoice side by side. Any credit changes the invoice, so it waits for the owner.
Sources
Checked October 20, 2026. Setup and capability descriptions use the live Omni pages below. Examples use fictional records and do not report customer results. Vendor figures, where retained, are dated records from the linked Omni comparisons; confirm current vendor terms before buying.
