2026-06-01 – Weekly Collections News : Software integration challenges

Last week, our community delved into a range of topics focusing on both practical challenges and strategic advice in the collections industry. Members shared their experiences with software integration challenges, offering insights into common pitfalls and solutions. There was also a lively exchange of tips aimed at newcomers seeking to enhance their call techniques. Recurring themes included technology adaptation and skill development, reflecting shared concerns and interests across the board.


This Week’s Hot Topics

Struggling with software integration issues
Members are discussing the hurdles of integrating new software into existing systems, with a focus on balancing efficiency and accuracy. This conversation is crucial for those looking to streamline operations without sacrificing data integrity.
Read more here

New collector looking for call tips
A thread has emerged for new collectors eager to improve their call skills, featuring practical advice from seasoned professionals. This discussion is a valuable resource for anyone looking to refine their communication strategies in collections.
Read more here


Looking forward to another week of engaging discussions. Stay connected and keep sharing your experiences and expertise.

When tackling software integration challenges, I’ve found that involving IT early on can really streamline the process. Last year, our team faced a major hiccup because we underestimated the tech complexities. Involving them from the start helped us avoid some major pitfalls.

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

I’ve seen success with regular check-ins during software integration. Engaging everyone, including IT, helps spot issues early. @Guide’s point about avoiding pitfalls is spot.

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

I totally agree with @Guide about avoiding pitfalls. In my past experience, setting clear expectations and timelines up front really helped keep everyone aligned. It’s amazing how much smoother the process can go when everyone’s on the same page from the start.

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

I’ve found that using a project management tool for tracking integration tasks can make a world of difference. Last year, we implemented Trello to visualize our progress and quickly identify roadblocks. It not only kept everyone on the same page but also fostered better communication among team members.

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

I’ve had my fair share of software headaches, too. One trick that worked for us was bringing in a third-party consultant to facilitate workshops; sometimes you need outside eyes to catch what your team misses. @rpatel12, it might sound like overkill, but it really boosted our collaboration and understanding.

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