Checks what's overdue
Faber reads the invoice list you already keep - a spreadsheet, or invoices sent and received by email - and works out what's unpaid and how late.
Use case
You set it up once - where your invoices live, how the reminder should read, and when it goes out. From then on Faber runs those same steps, finds what's overdue, sends the follow-up, reads the reply, and chases again on the date a customer promised to pay.
How it helps
Faber reads the invoice list you already keep - a spreadsheet, or invoices sent and received by email - and works out what's unpaid and how late.
A customer answers "I'll pay Friday." Faber notes the promise and follows up if Friday passes without payment, so nothing slips.
It follows the steps you set, in the same order, on every overdue invoice - so none get missed and no one gets chased twice.
What happened
After every run, Faber leaves a plain-English record of the reminders it prepared and the replies it read.
Good fit when
Invoices are tracked in a spreadsheet, or sent and received by email.
Follow-ups are written by hand today, and slip when things get busy.
Tone matters - reminders should stay polite and escalate gradually.
You want to see what was sent, what was promised, and what's still outstanding.
Describe where your invoices live, how the reminders should read, and when they go out.