Use case
Chase late invoices without the awkward emails
Ask Mojobase to chase overdue Stripe invoices unless you agreed otherwise. It reads them in Numbers, checks email, meeting notes, team chat and tasks, and skips agreed delays with the reason linked. The others get reminder drafts with the existing Stripe invoice payment link, from the right mailbox. A person checks and sends every reminder.
How does Mojobase chase late invoices, step by step?
Ask once
Type the request in Quick actions (⌘K), or ask your own agent: “Chase everything more than 14 days late, unless we agreed otherwise.” Save it as a scheduled run and the same check happens every morning.
Find what's overdue
Numbers → Invoices lists your company's existing Stripe invoices past their due dates, with the customer, amount and days late. Open and overdue totals also appear on person and company pages in Customers.
Read the emails
For each customer, the AI reads the recent threads. “Can we pay after the second delivery?” answered with “Of course” is an agreement, and that invoice waits.
Read the call notes
Notes on past meetings are checked too. A note from the 14th saying “hold 1042 until delivery two” takes Northside Bakery off the list, and the note is shown as the reason.
Read the team chat
The AI checks team chat and tasks too. If Sam wrote in #accounts that Harbor Cafe will pay at month end, or a task records a promise to wait, the invoice is skipped with that source linked.
Draft each reminder
The rest get a draft each from the right mailbox, in your Handbook's tone. It names the invoice, amount and due date and includes the existing Stripe invoice payment link. Mojobase does not create a payment page.
You read, then send
The reminder drafts wait in Email for a person to check, edit and send. Skipped invoices stay in Numbers with the reason and a link to the agreement's source.
Followed until paid
Each reminder gets a follow-up task. If the invoice is still unpaid by then, the next reminder is drafted; once it's paid, the task is suggested as done.
What do you say to start it?
- “Chase everything more than 14 days late, unless we agreed otherwise.”
- “Who owes us money, and since when?”
- “Why was Northside left out of the reminders?”
- “Draft a firmer second reminder to Harbor Cafe.”
- “Which customers have paid late more than twice this quarter?”
Why do late-payment reminders go wrong?
Because the reminder goes out without the context. A standard reminder lands on a customer you promised to wait for, and a good relationship takes a knock over a misunderstanding. Owners know this, so they check each one by hand, and that's why chasing gets put off for weeks. The agreement to wait is almost always in an email, a call note or a chat message, and in Mojobase all three sit next to the invoice, so the AI checks them before it writes a word.
What counts as an agreement to wait?
Anything in Mojobase that says the invoice shouldn't be chased yet. The AI shows you the source for every invoice it skips, so you can overrule it:
| Where it's found | Example | What happens |
|---|---|---|
| “Can we pay after the second delivery?” “Of course.” | Skipped until the delivery, with the thread linked | |
| Call notes | “Hold 1042 until delivery two”, noted on the 14th | Skipped, with the note shown |
| Team chat | “Harbor Cafe will pay at month end, agreed by phone” | Skipped until month end, with the message linked |
| Tasks | “Correct Harbor's invoice in Stripe”, still open | Held: a person needs to correct the invoice in Stripe |
| Support | An open complaint about the order the invoice covers | Held, and flagged for a person to decide |
| Nothing found | No agreement anywhere | A reminder is drafted |
What does a good reminder say?
Specific and easy to act on. It names the invoice, amount and due date, includes the existing Stripe invoice payment link, and mentions anything relevant you've discussed. The second reminder is shorter and firmer, and the third suggests a call. Each draft is in your tone, from the right mailbox, and you can rewrite it in a sentence: “warmer, they're a good customer”. A person sends each reminder; invoice creation, sending, numbering, PDFs, tax, payment pages and payment status stay in Stripe.
Why does it matter that the AI sees everything?
Because the expensive mistake isn't a missed reminder, it's a wrong one. A separate invoicing tool sees the due date and nothing else, so it chases the customer you made a promise to. Mojobase sees the invoice, the conversation and the call together, which is the only way “unless we agreed otherwise” can mean anything.
Questions people ask
Does the AI send payment reminders by itself?
The reminders wait as drafts for you to read and send. Scheduled runs, such as the morning sweep, only ever write drafts and suggestions, and Mojobase enforces that rather than leaving it to the model.
How does Mojobase know we agreed to wait?
It reads what's in Mojobase about that customer: their emails, your notes on meetings with them, the team chat and their tasks. When it finds an agreement, it skips the invoice and shows you the message or note that says so.
Where do the invoices come from?
From your company's Stripe account, connected with a restricted read-only key through Settings → Connections → Connect a source. Numbers → Invoices and each person's and company's page in Customers show those existing invoices and amounts owed. Stripe creates and sends the invoices; Mojobase reads them, in US dollars.
Does Mojobase see payments into my bank account?
No. Bank connections, bookkeeping and expenses aren't part of Mojobase. Invoice payment status comes from Stripe and is displayed in Numbers. If a customer pays by bank transfer, check that Stripe's status is current before sending a reminder.
Will the reminders sound like me?
Yes. Every draft follows the tone of voice in your Handbook's business profile and the style note on the address it's sent from, and you can rewrite any of them before it goes.