Why collection workflows need more than reminders
The standard automated answer to overdue money is a sequence of increasingly firm messages. It is cheap, it is easy to configure, and it converts the accounts that were always going to pay.
It does nothing for the accounts that are genuinely at risk, and it has a cost that is rarely counted.
What a reminder sequence cannot do
Five things, all of which the difficult accounts require.
- Know that this account already paid, and the money is sitting unmatched.
- Know that this payer agreed a plan in the office and is keeping it.
- Know that this charge is disputed and chasing it is the wrong action.
- Remember that this payer promised an amount by Friday, and whether the last three promises held.
- Decide that this account, of forty-seven, is the one worth a person's afternoon.
The cost nobody counts
Every reminder sent to someone who does not owe it spends a small amount of goodwill and a larger amount of credibility. Do it a few times and people stop reading your messages entirely — including the ones that are correct.
In membership organizations the cost is higher still, because the recipient is a member who will be in the room at the AGM and may simply not renew.
What a workflow adds
Collections as an operation rather than a broadcast has five properties a sequence does not.
- A queue that is ranked on recoverability and already excludes accounts on hold.
- An owner per case, so overdue money is somebody's job rather than nobody's.
- Memory: what was tried, what was said, what was committed to and whether it held.
- Instruments other than messages — arrangements, disputes, holds, escalation.
- Recorded outcomes, so the next cycle is informed by this one.
Automate the routine, escalate the judgment
None of this argues against automation. Reminders, statement runs, promise follow-ups and queue construction should all be automatic — they are mechanical.
What should not be automatic is the decision: granting an arrangement, writing something off, restricting access, escalating. Those need a person, and the record needs their name on them.