Last week, our “Collections” forum saw vibrant discussions around several key operational challenges and strategies. Members shared insights on optimizing sales stacks to improve placement rates and debated the effectiveness of propensity-driven channel mixes. There was also significant conversation around the operational impact of autopay systems when accounts reach a zero balance, as well as how score-tiered dialing strategies are performing with SMS integration.
This Week’s Hot Topics
Sales stack that actually feeds placements
This discussion centered on refining sales tech stacks to boost placement efficiency, a crucial topic for those aiming to streamline their operations. Read more here
Propensity-driven channel mix results
Forum members are analyzing results from using propensity models in channel strategies, highlighting what’s working and where adjustments are needed. Read more here
Autopay meets a zero balance
There’s an engaging thread on how autopay setups are handled when accounts hit zero, a must-read for those managing automated payment systems. Read more here
Score-tiered dialing with SMS results
This topic delves into the results of integrating SMS in score-tiered dialing strategies, providing valuable feedback for those using multi-channel approaches. Read more here
COB denials piling up after January resets
Members are tackling the challenge of increasing COB denials post-January, discussing strategies to manage and reduce these occurrences. Read more here
Dialer resets are breaking Reg F counts
A critical thread for those affected by dialer resets, which are reportedly disrupting compliance with Reg F. Read more here
Looking forward to another week of insightful discussions. Feel free to jump into any of these topics or start a new conversation. Until next week!
We had autopay keep firing the day after an account hit “zero balance” — , this drives me nuts. Our fix last week was a rule that pauses the mandate when remaining_balance <= next_scheduled_amount, cancels the recurrence, and fires a “paid off” SMS; the ACH token stays active for easy re-enroll. If you’re on ACH, sanity-check the final sweep against Nacha return logic to avoid accidental retries: Nacha Operating Rules - New Rules | Nacha.
We switched autopay to bill only the statemented amount and added an idempotency key per cycle so the job can’t fire again once the ledger says $0 — “no debt, no debit.” Small caveat: if you allow off‑cycle payments, run a last-minute pre-file check (e.g., 5 minutes before NACHA/card submit) and read the committed balance to catch late credits, @dan.
Moved the zero-balance guard into the ledger last week: the autopay job can’t persist a charge unless amount_due > 0, enforced by a partial index, so dupes die at write. We also emit a “zeroed” event that cancels any queued mandates in the scheduler. Only caveat: late refunds can re-open a few cents — rather than flipping the mandate back on, we fire a one-time top‑up.