Using a phone score to drive dialing strategies can be daunting for many companies. Complicated strategy products can be hard to test and a nightmare to implement. As Brandon Huisman explains, however, testing and implementing phone score can be simplified without changing effectiveness.
In our previous blog, “Pros and Cons of Different Batch Skip Tracing Tests“, we discussed three types of batch phone append tests you might use when trying to evaluate a new or existing skip tracing vendor. The three tests described were: champion challenge (overlap), champion challenge (A/B test) and a retroactive test. While each type of test has its pros and cons, each test also has varying skip tracing KPIs. We’ve outlined the key performance indicators, how to measure them and what tests they are best suited for.
Adding a new data provider to your skip tracing process can come with some unknowns, but when goals and objectives are laid out clearly, both the vendor and the client are able to execute testing and implementation more effectively. At LocateSmarter, we want to make sure our prospective clients are set up for success, so we have outlined three of the most common batch skip tracing tests. Which test you decide to execute will depend on your collection software, internal resources and time.
We continue our Meet the Team series with Brandon Huisman, Manager of Analytics at LocateSmarter. Brandon started off his professional career in the mortgage industry before moving to collections and data. His numbers-driven approach has helped to improve both our products’ performance and our clients’ collection and dialing strategies, resulting in more RPCs and operational efficiency. In this blog, Brandon talks about the importance of call/account disposition data, his role as Manager of Analytics, and why it took him three days to find his car in 2008. Continue reading to learn more about Brandon Huisman…