Sports coaches talk about marginal gains, and how lots of small changes can add up to the difference between winning and losing in a tight contest. But if Gareth Southgate found a new strategy that would boost his team’s performance by 200-300%, he’d jump at the chance.
That’s the level of improvement delivered by outbound dialling software over manual dialling. Like any good team performance though, it’s about getting the right balance right, in this case between reaching new targets and remaining compliant with Ofcom regulations.
Where Does the Productivity Leap Come From?
Some of the productivity gains from outbound dialler software are built on predictive dialling, in which calls are placed at a rate the dialler expects agents to become free from their previous conversation. Calculating this rate is done by the predictive algorithm.
Predictive dialling is supported by two further modes, progressive and preview dialling. In progressive mode, the dialler waits to make the call until the agent becomes free, rather than estimating that time in advance. Preview dialling allows the agent to review information about the contact before the call is made.
All three modes have a role to play, and getting the right combination means agents typically spend two to three times longer actually talking to clients, and so meeting the overall aims of the business, than if they were managing their own calls manually.
Real World Conditions
In a perfect world, a predictive dialler would make outbound calls at a rate that always exactly matched the agents available to connect to clients.
But it’s never that simple. Instead, let’s run through some of the ways outbound dialling can get out of sync, and ask what the consequences are.
The most obvious way is that agents are people. They log in and out unexpectedly. They have to go for meals and comfort breaks.
Then there are blended environments. Agents taking inbound calls means that they aren’t available for outbound calls, and so the predictive algorithm gets the rate of outbound calls wrong. Blended environments are like a football match against Brazil. They’re always going to be tough.
In effect, there’s always the risk of an avoidable own goal, which simply means making too many outbound calls when there aren’t enough agents available to cope.
All of these real world conditions lead to dropped calls. And dropped calls aren’t the only compliance challenge. Redialling the same number too soon after a dropped call can be an issue if not handled properly. As is repeatedly dialling a number that has asked not to be called.
Then there are silent calls. A silent call is when answer machine detection (AMD) registers a false positive, meaning a person answers but the dialler software thinks it’s an answer machine and hangs up.
“For some people – for example, those living alone – these calls can be particularly frightening,” says Ofcom.
So what is the penalty for getting compliance wrong? For serial offenders, it can mean a potential fine of up to £2 million.
Ofcom and the 3% Myth
In order to get compliance right, the first step is separating facts from myths.
There are two persistent compliance myths in the call centre industry.
The first is that Ofcom specifies a target of 3% for dropped calls. Some software diallers might even be calibrated to produce 3% dropped calls and claim this is compliance.
This is not the case. Ofcom wants to see 0% dropped calls, and a contact centre operator needs to demonstrate they are doing everything they can to achieve that. The 3% figure is a benchmark. It means that so long as an operator is doing all they can to minimise dropped calls, Ofcom accepts that mistakes can and will happen.
The second myth is that a dropped call number cannot be rung again within 72 hours. Wrong again. What matters is that an agent must be on hand if the call is answered.
Balancing Productivity and Compliance
A dialler software solution that can deliver outstanding productivity gains without putting compliance at risk will have a checklist of key features.
It should head off the causes of dropped calls before they happen. That means agents have to request their next action, such as logging off. Given this information, the predictive dialler can adjust its outbound call rates to match.
In blended environments, the predictive algorithm has to allow for inbound calls.
The dialler should move seamlessly from predictive to progressive dialling at times when there are fewer agents, for example during lunch breaks.
When recalling numbers within 72 hours, the dialler should switch to preview mode so that an agent is guaranteed to be available if the call gets through.
It should eliminate silent calls due to AMD by passing the call to an agent if there is any doubt, and should leave a message in any circumstances where a call isn’t picked up, completely avoiding any silent calls.
Finally, the dialler software should automatically integrate and update Do Not Call lists, and allow clients to add themselves to the list.
This blog post has been re-published by kind permission of MaxContact – View the original post
To find out more about MaxContact, visit their website.
Call Centre Helper is not responsible for the content of these guest blog posts. The opinions expressed in this article are those of the author, and do not necessarily reflect those of Call Centre Helper.