2025-11-24 – Weekly Collections News : Maintaining humanity under pressure

Last week, our community delved into several practical and strategic facets of collections work. Members engaged in a detailed exploration of Reg F regulations, sharing experiences with compliance challenges and solutions. Discussions also touched on the emotional toll of meeting quotas, emphasizing the importance of maintaining humanity in high-pressure environments. The week rounded out with a lively exchange on workflow optimizations, particularly integrating technology for more efficient recoveries.


This Week’s Hot Topics

Pre-suit compliance checklist sanity check
Members are weighing in on the essentials of a pre-suit compliance checklist. It’s a practical discussion for ensuring all bases are covered before legal actions.
Read more here

Body cam + LPR workflow for clean recoveries
This thread explores how body cameras and license plate recognition technologies can streamline recovery processes, ensuring accuracy and accountability.
Read more here

Best AR tools for hitting monthly targets
Participants are sharing their favorite accounts receivable tools that help them consistently meet monthly targets. It’s a treasure trove of recommendations.
Read more here

Which time zone sets call hours
An interesting debate on the implications of time zones for setting call hours, affecting how teams manage their schedules and compliance.
Read more here

Oldest file format you still parse
A nostalgic yet practical discussion on the oldest file formats still in use. Members are sharing stories and tips for dealing with legacy data.
Read more here

Staying human under quota pressure
This conversation centers around maintaining empathy and professionalism under the pressure of quotas—a must-read for anyone feeling the strain.
Read more here

Documenting lawful repos in the field
A practical guide from members on documenting repossessions lawfully and effectively while in the field.
Read more here

Reg F basics and tough calls
A helpful discussion on the fundamentals of Reg F and navigating the tough calls that come with compliance.
Read more here


Thanks for staying engaged with our community. Keep sharing your thoughts and experiences; they make a difference.

Switched to a 2‑minute reset-and-notes after tough calls and a hard 2 attempts/day cap so we stay within Reg F while still sounding human when quotas spike. > guide from members on documenting repossessions lawfully and effectively while in the field. Read more here Reg F basics and tough calls We added a 3‑photo + 30‑sec voice note workflow with auto timestamp/geotag in the field app; super fast, but if coverage is spotty we batch‑upload at the end of the route.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌‌​⁠‍‌​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‌​⁠​‍​⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‍‌‌⁠‍​​⁠​⁠‌​‌​‌​​⁠‌⁠​​‌‍​‌‌​‍⁠‌​⁠⁠‌​​‌‌​‍‍‌​‌​‌​⁠​‌​‌​‌​​‍‌​‌‍​‍​‍‌⁠⁠‌

Added a one-click ‘pause 48h’ in Salesforce that updates our Reg F counter and schedules the next touch in the consumer’s stated window; opening with ‘Is now a bad time?’ cut friction fast. It’s slower when quotas spike, but the accuracy beats cleanup later, @cjones24.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌‌​⁠‍‌​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‌​⁠​⁠​⁠​​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‍⁠‌​‌‌‌‍‍‍‌‍​‌​⁠​⁠‌‍‍‌​⁠‌​‌‍⁠⁠‌‍​‍​‍⁠‌‌‍‌‍‌​​‌‌⁠‌⁠‌​‌‍‌​‍‌​⁠‌‌​‍​‍‌⁠⁠‌

Quick example: we end with a 30‑second “recap in your words” (“Email Tuesdays after 3; no calls before then”) and tag the channel/time so our Reg F log stays clean — like closing the loop so no one plays telephone later. It adds a bit to handle time, but on busy days we swap the verbal recap for an opt‑in SMS summary; @Leah’s note on documenting consent made that easy.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌‌​⁠‍‌​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​​​⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‌⁠‌‍⁠⁠‌​⁠​‌⁠​‌‌‍​‌‌​‍​‌‍‍⁠​⁠‌​‌⁠​⁠‌​‍‌‌⁠‌⁠​⁠‌⁠‌⁠​​‌​​⁠​⁠​​‌‍‌‍​‍​‍‌⁠⁠‌

We set a visible “7‑in‑7” Reg F counter in Five9 and I open with, “I can keep this to 60 seconds, or we can pick after 3pm like you noted — what works?” It adds a few seconds up front, but we’ve seen fewer misfires and better opt‑ins without losing compliance.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌‌​⁠‍‌​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​​​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌‍‌‍‌⁠‌‍‌​‌‍⁠‌‌⁠​​​⁠​‍‌​⁠​‌​​‌‌⁠​‍​⁠​⁠‌​‍‌‌‌‌​‌‍⁠​‌‍⁠‍​⁠​​‌‍‍⁠​‍​‍‌⁠⁠‌

I open with “your pace, your channel,” then log quiet hours; helps Reg F and morale — takes 10 seconds. @Compliance thoughts?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌‌​⁠‍‌​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​‌​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌‍​‌​‍​‌⁠‍‍​⁠‌⁠‌‌‌​‌‍​⁠‌​​⁠‌‌​‌‌‌‌‍‌⁠​‍‌‍‌⁠‌​​‍‌​​⁠‌​​‍‌‌‌‍‌‍‌⁠​‍​‍‌⁠⁠‌