Changelog

We rebuilt the site around the real thing. Every screen you see is the actual FetchDue dashboard — the command center, your invoices, the chase view, sent replies — not stand-in mockups. What you look at before you sign up is what you get after.

There's a new how-it-works page that walks through the whole loop in plain language: FetchDue reads a reply in your mailbox, drafts the next message, and waits for your approval before anything goes out. We also cleaned up the footer and added proper legal pages, so the boring-but-necessary details are easy to find.

Polite persistence with real teeth. FetchDue's escalation ladder ramps the tone as an invoice ages, and it pauses the cadence automatically while a client conversation is live — no reminder talking over a reply.

For the bookkeepers who run collections across many agency clients, the firm console rolls every client's receivables up into one view.

"Can we split this?" used to mean a reminder blasting into the middle of a negotiation. Now FetchDue recognizes the ask, drafts a payment plan — installments with real dates — for you to approve, and then tracks each promised payment. If one slips, it follows up on that installment instead of starting over.

When a client replies, FetchDue reads it, works out what kind of reply it is — a question, a promise to pay, a request to split the bill — and drafts the right response in your voice.

Approve-before-send is structural, not a setting: every draft waits for your one click. The agent does the work; you keep the final say on every message.

An invoice is not a one-way reminder — it is a conversation that unfolds over weeks. FetchDue now models it that way. Every message in both directions lives in a single thread tied to the invoice, so the agent (and you) always have the full history: what was said, what was promised, and what is still open.

Connect your Microsoft 365 mailbox and FetchDue starts listening. Every reply a client sends about an overdue invoice lands back where the agent can see it — in near real time, with a polling fallback so nothing is missed.

This is the foundation for everything the agent does next: it can only chase well if it can hear the client answer.