Informizely customer feedback surveys
By using the Aculab site, you agree with our use of cookies.

Contact centre technologies – issue ten

Hello, from Aculab call central.

In this post, the tenth of tonnes, I’ll look at how the benefits of diallers and customer interaction solutions are viewed. You’re welcome to post any questions in the comments section below.

In the last post, which you can view here, I looked at some of the benefits of using diallers, in general. This time, I’ll take a look at the first of two areas in which the benefits of using call progress analysis (CPA) in conjunction with diallers are often judged.

Comparisons

Judgements are made by comparisons involving: i) lost agent time; and ii) connection accuracy. Those judgements are often presented by some of the more prominent vendors of contact centre solutions as a kind of gospel – almost a sacred text.

Comparisons invariably focus on post-connect CPA, however, it should never be overlooked that pre-connect signalling detection is equally, if not more, invaluable for a dialler system. Good pre-connect CPA is vital for fast and accurate decisions to continue with a call attempt.

The theory of lost time

The widely promulgated theory of lost time assumes, for the sake of its argument (which is designed to prove that diallers are essential), that all calls are connected and agents have the task of determining who or what is on the line. It also assumes that the handling time for an agent to wrap up a falsely connected (i.e., it’s a machine on the line) call is 30 seconds.

That being the case (so the theory goes), multiply the 30 seconds by a large number of machine answered calls per day (choose your own number; it’s as much as 60 percent of all calls), multiply the result by 261 agent days per year, multiply that by ’0 dollars per hour and you end up with a ballpark number in the ‘00s of ‘000s, which sum is then presented as the huge cost (saveable if you use a dialler to screen calls) of handling unproductive calls.

But…

Unfortunately, the theory is flawed as it focuses on the polar opposite of what really matters, never mind that it can’t possibly take 30 seconds to wrap up a call answered by a machine.

You don’t use a dialler to save wrap-up time on falsely connected calls. You use a dialler to: i) avoid wasting valuable agent time dialling numbers; and ii) reduce wait times between calls. Waiting time is that between wrap-up and the next live connect, which incidentally, is the concern of a dialler system and not an aspect of CPA.

Agents can only take a call when they’re free. When not free, they’re as productive as can be. In reality, the number of calls made is not a constant; it’s neither static nor linear, but related to the number of available agents. As an agent becomes free or additional agents log on, the dialling rate goes up. The beauty of diallers is that they adjust the dialling rate to be able to connect a call immediately an agent is available.

Focus

Furthermore, it’s surely better to focus on productivity gains than cost reduction. I suggest an increase in the collections or revenue per agent figure would be a far more sensible metric on which to concentrate.

Perhaps the purveyors of perceived wisdom are not as wise as they’d like you to think.

Stop by again next week for another instalment in this useful sequence of posts. Ciao!

Joeb Logger Avatar
  - Joeb Logger

Archive

The Aculab blog

News, views and industry insights from Aculab

  • Jail time for biometrics

    The people who work in the Broadville Retention Centre, a temporary home for semi-retired hoodlums, love working there. The centre in south-west London, England, has views of flightpaths from Heathrow Airport; sights evocative of the freedom temporarily denied its residents. Workers at the centre on the other hand enjoy freedom of movement, not only in coming and going according to their shift patterns, but also within the building complex.

    Read more

  • Aculab Cloud and the EU GDPR

    The EU General Data Protection Regulation (GDPR) is important to Aculab and its customers in the EU region, and also for our non-EU customers who use Aculab Cloud for their customers who reside in the EU. This is a summary of what we have done to ensure the privacy and security of customer data on Aculab Cloud.

    Read more

  • Preparing to meet the EU GDPR rules with Aculab Cloud

    Firstly, lets establish what the GDPR is, and why it’s important to Aculab and its customers in the EU region, and also for our non-EU customers who use Aculab Cloud for their customers who reside in the EU.

    Read more

  • Improved Aculab Cloud documentation and a new console

    We’ve been busy in the background recently at Aculab with a major website refresh. Aculab has evolved over decades (40 years this year!) from a vendor supplying hardware to a much more software-centric product company. We still sell telecom gateways extensively, but nowadays the bulk of our enabling technology business is software, and in particular our communications platform-as-a-service (CPaaS) product, Aculab Cloud.

    Read more

  • Interoperability is predictable

    Way back in 2007, while presenting a seminar in Prague, someone asked me for my prediction on when SS7 would no longer be in use. My answer was suitably vague, but something on the lines of, “at least 10 to 15 years.” Ten years on, I wasn’t wrong. Still, I may not be right. SS7 is showing its age, but it’s not about to draw its pension just yet.

    Read more