Dialers today consist not only of mass campaigns intended to call as many numbers as possible in a given timeframe, they are also becoming increasingly more analytic in nature. Not only does an enterprise dialer analyze current staff levels (and what your staff is currently doing) to pace itself, it also analyzes data stored internally or interfaced to it, to provide the right time to contact your customers based on your strategy. Today’s dialers also provide Application Programming Interfaces (APIs) to provide transparency in communications with applications. We enhance the overall dialer experience by allowing you to decide how you use your dialer with COLLECTIONS.

Back-Office

COLLECTIONS handles the traditional daily upload file for delivery to your dialer system, containing the fields you select and only those accounts your strategy dictates. We also handle the traditional "kill file" consisting of accounts to be excluded (for events configured by you to be excluded) from the dialer’s remaining calling activities for the day. The timing of this exclusion file is at your discretion: you decide.

Desktop

Our COLLECTIONS desktop application provides seamless communications to any third-party Dialer providing an API via our .NET Dialer architecture. The API itself may be COM or WebServices based. We fully integrate with the major dialer products in the marketplace today.

The end-user experience is enriched by allowing the collector to work within and only within COLLECTIONS. The benefits range from a less-cluttered desktop to potentially large license savings by retiring existing Dialer vendor-provided desktop software. Gone are the days where the user has to flip between windows just to work!

We do this by providing a small toolbar that handles all communications between the user and the dialer, from within COLLECTIONS. There are certain features all dialers perform and require, while at the same time each dialer strives to differentiate itself from the others. We implement these functionalities by feature-sets, whereby you tell us what features you want enabled/disabled based on the type of dialer.

Lastly, our .NET architecture and toolbar allows COLLECTIONS to handle multiple dialer types by the same customer without changing user-facing presentation and without giving up functionality. This allows you to have, if you wish, one dialer for doing something well, and keep a different dialer for doing something else well. Again, it’s your choice.