Most collections software treats a late invoice like a confrontation. It isn't. When a business collects on money genuinely owed to it — first-party collections — the goal is to get paid while keeping the customer. Those two goals aren't in tension. They reinforce each other.

The cost of getting it wrong

Aggressive dunning has a hidden price: the customer who pays once and never comes back. For a service business, the lifetime value of a recovered relationship dwarfs a single overdue invoice. Treating people like delinquents optimizes the wrong number.

There's a compliance cost too. Even first-party creditors operate under TCPA, state usury caps, and quiet-hours rules. Software should make the compliant path the easy path.

A calmer playbook

Here's the cadence we built into Collect, in order of escalation:

1. A friendly reminder a few days after the due date.
2. A short SMS with a one-tap payment link — only if the client consented to texts.
3. A settlement offer or payment plan, framed as help, not punishment.

Every step re-checks state at fire time. If the client already paid, the step skips with a logged reason. Nobody gets chased for money they've handed over.

What "firm but humane" looks like in code

The two rules that matter most:

• Stop instantly on payment. A sequence that keeps texting after someone pays isn't just annoying — it erodes every future interaction.
• Respect quiet hours. No 2 a.m. payment reminders. The sequence runner enforces 8am–9pm client-local before any SMS goes out.

// The sequence runner re-checks before every step.
if (await invoice.isPaid()) {
  return skip("already paid")
}
if (!withinQuietHours(client.timezone)) {
  return reschedule(nextMorning(client.timezone))
}

The result

Businesses on Collect resolve the large majority of overdue balances inside the sequence — without a phone call, and without burning the relationship. That's the whole point: firm, never cruel.