ACD Call Routing: What Happens When an Agent Misses The Call?

With Asterisk ACD Systems, or any ACD Software, one has to take into account the agent’s behaviour. One issue that can happen is an ACD call is routed to an agent due to indicating they are ready but are not able to accept the call at that time.

They may miss the pop-up on screen prompting them to accept the call. Or perhaps they are On-Hook and are distracted and unable to answer the call in time. Answering the phone while in On-Hook mode or clicking to accept the call are both forms of acknowledgement which when received bridge the caller and agent together.

What happens when this acknowledgement is missed?

This will depend on the configuration. Systems will offer two key settings related to these missed ACD calls. First is how many times to allow calls to be missed, if this is allowed then the agent will go back to being ready for a call after missing the acknowledgement. The second setting is related to how quickly they will go back to being ready. It’s typically best for the caller experience to not put them back in automatically until the agent indicates they are ready, however some situations will have agents missing the occasional call and then it makes sense to put them back after a few seconds.

No matter the reason or configuration when these cases happen we still need reporting to let us know what is going on with the system and agents.

Connecting Call Center Agents

It looks like there’s a common theme running through recent blog posts. At the Indosoft blog this week, I wrote “Remote Agents in the Modern Call Center” discussing connecting at-home and remote groups of agents to a call center.  This seems like an obvious expansion of the Cloud to call center concept.

I had originally considered talking about connection methods in my post, but at the last moment cut it out as not being as important. That is a topic that was covered last Friday by Shaun, who wrote “Connecting Agents to the Call Center ACD” which talks about the types of devices an agent can use to connect in.

A couple of weeks ago, Brian wrote “Agent Connections With an ACD System” which discussed on-hook and off-hook agent connections, as well as VoIP vs. dial in or dial out connections for agent phones.  Between all three posts, I believe the topic of connecting agents to a call center is pretty well covered.

Populating Client Information to Agents in Your ACD – Part 1

One of the major purposes of many inbound call centers is customer care.  Clients may call with technical issues, be updating their orders, or enquiring about new services. In this case, it’s obviously important to ensure that the agent handling the call have as much information as possible about the caller. The question becomes how do you get those details into your call center software and in front of agents?
Continue reading “Populating Client Information to Agents in Your ACD – Part 1”

Rapid Reconfiguration of Servers For Cloud-Based Call Centers

Hosting your call center software in the Cloud, as regular readers of this blog know, allows for a flexibility in the allocation of resources that is simply not available in on-premise call centers. In a large call center deployment, a number of servers are usually provisioned for specialization: web servers, database, telephony, etc.. Changing conditions can mandate that the mix of servers should change over time. In these circumstances, it is important to have the ability to quickly repurpose a server. Continue reading “Rapid Reconfiguration of Servers For Cloud-Based Call Centers”

Priority Skills in ACD Systems

In previous posts I have mentioned the need to properly configure and staff queues to meet the needs of your customers.  Using ACD Skills with priorities plays an important role.

Skills are initially seen as a way to get an agent logged into their proper queues. Which is true if all the priorities are equal. Using priorities on skills allows for fine grain control to ensure the best trained agent available will get the appropriate caller.

Lets take language as an example, but this could also apply to different products or categories being handled.  With language lets say you have a three groups of agents.  The first is native english speakers who also speak french as a second language.  The Second is native french speakers with english as a second language.  With the third being  those agents who only speak english.

The first and third group would both have the “English” skill with a high priority.  However the first would also have the “French” skill at a lower priority than the second group, the native french speakers, which allows them to help with the french queues during high call volumes.  A similar configuration reversed for the native french speakers who also speak english would be setup so they can in turn help with high call volumes on the english queues.

Doing this makes the queues more efficient as there are more people staffing to help during the high times but priorities on the skills ensures their primary queue is still staffed and calls handled in a timely manner by the highest skilled agent available.

This can also be extended to supervisors who only occasionally take calls, perhaps during high volume periods to keep up with the extra inflow of callers.  The supervisors can be set to lower priority than the agents so they would only get calls when no agents are available for the queue.

There are many other cases where skills and priorities can be used to meet the needs of the business case at hand.

High Availability Asterisk Solutions

Asterisk High Availability (HA) solutions, once reserved for mission critical deployments, are now commonplace in normal contact center setup. With VoIP, clustering solutions make it relatively straightforward to move IP traffic. Setting up a main and standby Asterisk system will allow such an arrangement to ensure continuous availability of an Asterisk system. Since telephony systems are not mere data systems using IP traffic, such arrangements to ensure immediate availability of the system is inadequate in ensuring the continuation of the calls that were underway when a hardware or software failure happened. Voice solutions require better options. One such option is the call survival capable high availability for Asterisk systems based on US Patent US 20110310773 A1 – a method and system for fail-safe call survival.

One of the most exciting technology to shake the telecommunications landscape in the last decade is Asterisk. Its use in unified communications (UC) and contact centers is unparalleled. Therefore high availability solutions for Asterisk have gained significant attention.  The high availability implemented using the above mentioned patent provides the technology to recover calls and successfully continue the on-going calls and conversations in the event of a failure. This technology is available as a part of a call center ACD that manages and scales to multiple Asterisk servers in a cluster to handle very large call volumes.

Enhanced multi-channel ACD routing to improve call center software efficiency

A multi-channel ACD does not imply separate queues for queuing different media  like voice, email, and social media. As a matter of fact, voice media might have many queues to take advantage of skills-based routing and queue priority. One reason to have exclusive queues for different media type is to simplify skill-set assignment. The more important consideration is to retain the ability to handle the different media calls judiciously with the realization that certain media type requires synchronous real-time communication while others require timely response, not necessarily real-time and synchronous. We know that voice conversations are real-time responses whereas emails require timely response in keeping with good customer service practice. This blog will review multi-channel ACD queue setup for skills based routing and discuss aspects of multi-channel media handling using enhanced features within a call center software.

Queuing and routing within a call center ACD is dictated by skills based routing and queue priority. Queues require specific skills to handle the voice calls, email, chat, or social media. Skills are dictated by the business requirements. For example, ability to conduct a conversation in English, Spanish, or French would each be a skill. Similarly, ability to answer customer inquiries on a specific product can be a skill required for handling calls coming into a specific queue. Writing skills and responding appropriately can be a skill essential for handling emails. Queues also have a priority that differentiates the level of service offered. A higher priority queue means it requires quicker response. Service is usually measured in terms of the average duration a customer waits before a call is handled. Employees who are involved with handling calls in the queue are assigned skill levels for the skills they possess. When an employee is logged into the call center ACD, their skills dictate the media calls they can handle and the skill level dictates the pecking order.

Queue priority is another important factor in the management of the service level within a contact center ACD. A higher priority queue will be handled before a lower one. When an employee becomes available, he or she gets the media from the highest priority queue for which they have the skills. Now let examine how to introduce efficiency in a multi-channel ACD with skills based routing and queue prioritization.

An emails do not require real-time synchronous response and therefore can be in a lower priority queue compared to a voice call. If an agent is offered an email from an email queue by the contact center ACD based on the skills based routing, it indicates that there were no calls waiting in any higher priority queue. When the employee starts working on the email response, a call can come into a voice queue that may require a faster response. With advanced call center software offering powerful ACD features like ability to re-queue media calls into a personal queue and make out of band announcement of calls waiting in higher priority queue, the employee handling an email can quickly re-queue it back into the ACD and be ready to handle the voice call. Here too, it can be re-queued into a personal queue that belongs to the employee so that they continue where they left off when it comes back to them. Such contact center ACD features will contribute to increase in the call center efficiency.

Using Q-Suite’s Call Monitoring Features to monitor Call Center Representatives to improve Customer Satisfaction and First Call Resolution

Call Monitoring features are a must for any call center.   Call Monitoring has many uses with in a business ranging from employee training to  quality assurance and complaint investigation.

How is Call Monitoring useful for training new customer service representatives? Continue reading “Using Q-Suite’s Call Monitoring Features to monitor Call Center Representatives to improve Customer Satisfaction and First Call Resolution”