A friendly note about invoice INV-0142
Hi ,
Just a gentle reminder that invoice INV-0142 for ₹48,000 is due on 26 March. If it is already on its way, please ignore this note and accept our thanks.

Chasing unpaid invoices without manual effort. Reminders run automatically before the due date and after it, and the sequence stops the moment payment is received.
Hi ,
Just a gentle reminder that invoice INV-0142 for ₹48,000 is due on 26 March. If it is already on its way, please ignore this note and accept our thanks.
Gentle reminder
sent 26 mar 09:00 istPolite reminder
sent 29 mar 09:00 istFollow-up
sent 01 apr 09:00 istFirmer reminder
next · step 4 of 5Final reminder or escalation
sequence stops the moment the money lands.
Stop on paid
Reminders run before and after the due date, and the rail keeps moving until payment lands. The instant an invoice is marked paid, the remaining steps are struck from the schedule — no reminder is ever sent after payment is received.
No send after paymentsequence stops the moment the money lands · paid 12 Mar
Timezone-based scheduling
Before a reminder leaves the queue, its send time is resolved in the configured timezone, so the client receives it at the hour you chose rather than at whatever clock the server happens to be running.
BlockedSend times are resolved in the configured timezone before dispatch.
Import · column map
Every column in the sheet lands in a named invoice field, so nothing is guessed on the way in.
Imported invoices are scheduled against the configured reminder sequence — the same T-3, DUE, T+3, T+7 and T+14 steps, stopping the moment payment lands.
These are the rules the product holds to — every one of them applies to every invoice, without exception.
The sequence halts the moment an invoice is marked paid.
Default wording for every step stays polite and non-aggressive.
Every message a client receives is one the user has approved.
Send times are resolved in the configured timezone before dispatch.
Each send records invoice reference, recipient, sequence step, and send time.
Politeness is a constraint here, not a preference. Reminders stay calm by default, and nothing goes out once an invoice is paid.
Five kinds of people send invoices and then wait on them. The reminder sequence does the waiting for them, in the tone they choose.
Small teams running receivables across many clients who need consistent, polite follow-up.
Maintain invoice records and payment status on behalf of client businesses, with an auditable trail.
Independent advisors who want chasing money to never depend on remembering to send an email.
Solo service providers who invoice clients directly and have no finance department.
Small service businesses that want calm, reliable automation rather than an enterprise billing suite.
Total value of invoices past their due date and still unpaid.
Total value of invoices marked paid.
The upcoming scheduled reminder sends across the book.
Sequence holds until paid
Already sending reminders? Log in
Sequence stops the moment the money lands.

Chasing unpaid invoices without manual effort. Reminders run automatically before the due date and after it, and the sequence stops the moment payment is received.
Hi ,
Just a gentle reminder that invoice INV-0142 for ₹48,000 is due on 26 March. If it is already on its way, please ignore this note and accept our thanks.
Gentle reminder
sent 26 mar 09:00 istPolite reminder
sent 29 mar 09:00 istFollow-up
sent 01 apr 09:00 istFirmer reminder
next · step 4 of 5Final reminder or escalation
sequence stops the moment the money lands.
Stop on paid
Reminders run before and after the due date, and the rail keeps moving until payment lands. The instant an invoice is marked paid, the remaining steps are struck from the schedule — no reminder is ever sent after payment is received.
No send after paymentsequence stops the moment the money lands · paid 12 Mar
Timezone-based scheduling
Before a reminder leaves the queue, its send time is resolved in the configured timezone, so the client receives it at the hour you chose rather than at whatever clock the server happens to be running.
BlockedSend times are resolved in the configured timezone before dispatch.
Import · column map
Every column in the sheet lands in a named invoice field, so nothing is guessed on the way in.
Imported invoices are scheduled against the configured reminder sequence — the same T-3, DUE, T+3, T+7 and T+14 steps, stopping the moment payment lands.
These are the rules the product holds to — every one of them applies to every invoice, without exception.
The sequence halts the moment an invoice is marked paid.
Default wording for every step stays polite and non-aggressive.
Every message a client receives is one the user has approved.
Send times are resolved in the configured timezone before dispatch.
Each send records invoice reference, recipient, sequence step, and send time.
Politeness is a constraint here, not a preference. Reminders stay calm by default, and nothing goes out once an invoice is paid.
Five kinds of people send invoices and then wait on them. The reminder sequence does the waiting for them, in the tone they choose.
Small teams running receivables across many clients who need consistent, polite follow-up.
Maintain invoice records and payment status on behalf of client businesses, with an auditable trail.
Independent advisors who want chasing money to never depend on remembering to send an email.
Solo service providers who invoice clients directly and have no finance department.
Small service businesses that want calm, reliable automation rather than an enterprise billing suite.
Total value of invoices past their due date and still unpaid.
Total value of invoices marked paid.
The upcoming scheduled reminder sends across the book.
Sequence holds until paid
Already sending reminders? Log in
Sequence stops the moment the money lands.
No comments yet. Be the first!