A priority for any new call center installation, once calls are being successfully dialed, is making those calls at the lowest cost. Trunk usage charges are a very visible number, and a tempting target for savings. It is vital that call center software offer a means of ensuring that calls get dialed in an economical manner. An Asterisk Cloud-based call center should be no different. Continue reading “Trunk Selection and Cost Control – Simple Least Cost Routing”
Adding Complexity to the Inbound Call Center ACD
In a prior post, it was shown that preparing a simple inbound ACD scenario can be fairly straightforward. This post will illustrate a few of the more complex components that can be leveraged in Q-Suite’s dialplan builder. Continue reading “Adding Complexity to the Inbound Call Center ACD”
Voicemail in a Multi-Server Environment
It’s very often the case that when using Asterisk-based call center ACD software, we want some calls to be directed to a voicemail box. This may be simply a call to the extension of someone who is busy or away from their phone, or could be a community voicemail for callers who have exited the queue. Continue reading “Voicemail in a Multi-Server Environment”
Cloud Storage in the Call Center
Over at the Indosoft blog I made a post about Cloud storage in the contact center. Using the Cloud for storage when your call center is already in the Cloud is a no-brainer. However, we are seeing the adoption of Cloud-based storage for on-premise call centers as a way to get around some of the issues that arise when archive recordings. Some of the post may be of interest to readers of this blog, so I encourage you to give it a read.
ACD Queue Features useful when the Caller Abandons the Queue.
With today’s busy world callers are in a hurry and want have their call handled promptly. However when calling during high call volume periods they may not wait in queue until an agent is available. In a recent post I talked about core ACD Queue features but lets look a few abandoned queue calls features.
Call Back – as described in my previous post gives the caller an option to leave a callback number and have an agent call them once available. The benefit here is the caller is allowed to disconnect and not feel their time is being used up waiting in queue. One potential issue is when the agent calls them back their phone could be busy or they are unable to answer it. In these cases ensure the re-attempt rules are setup so the caller doesn’t get lost and is still called back in a timely manner, while not re-dialing to often. A message on their voicemail will help to avoid this. This is not a true abandon call as they used a process to leave the queue.
In the cases where the Call Back feature is not enabled or is but not used by the caller it may still be desirable to follow up if they abandon out of the queue. When configuring the system for abandon calls there are a few options:
The abandon calls stays in the queue and keep position. This means their call is handled in the order they called in, so it will follow the ACD parameters setup for that queue. This allows the agent to attempt a call back with the CID or other information the IVR collected information may collected prior to the queue.
The abandon calls moves to another queue. This means their call is moved to another queue which allows for different ACD parameters to distribute the call. This can allow abandons to be a lower priority but we want to get back to them in time, so the center is setup to prioritize the live call queue and the abandons get handled during lower periods. Alternatively a different set or subset of agents based on their skills will only handle the abandons.
In both of these situations you may want to enable deduplication of abandons. When enabled if a caller calls in and abandons then does this multiple times before their first call record is handled they will only have one position in the queue. For productivity it makes sense to have this enabled so agents are not wasting time dealing with repeated records or worse two agents calling the same caller back due to two abandons in the queue with their info.
Bringing Instances Up and Down to Improve Performance and Save Money
One of the advantages of deploying a feature rich call center software suite in the Cloud is that there are feature rich APIs and tools available for managing both software and cloud infrastructure. The APIs of more advanced Cloud providers are of interest where they allow a call center to bring pre-configured instances up and down on demand. This can result in a significant cost savings when a major factor in the cost of the service is CPU usage. Continue reading “Bringing Instances Up and Down to Improve Performance and Save Money”
From Call Center to Contact Center
The changing marketplace is quickly bringing about new technologies for communication including e-mail, Twitter, and SMS. Increasingly, consumers are moving to these new mediums and expecting businesses to do the same. Staying on top of these fast growing channels of communication can provide an edge to the contact center of the future.
Continue reading “From Call Center to Contact Center”
Agent Connections with an ACD System
ACD Systems at their core provide a method to connect a caller to an agent. Lets look at the options for the agent side of this connection. Traditionally the Off-Hook nailup was the way to accomplish this. This works great for a dedicated agent who is taking calls from ACD queues one after the other at a high volume call center. It’s more efficient in that case to stay Off-Hook and save on the time of hanging up and answering the next call when the system can just bridge you to a new caller once you are ready. In my last post I looked at our in-house case where our support department handles inbound requests in a unified communications configuration. This use case is not call after call, but they will handle a call then an email or ticket so staying Off-Hook is not desired and this where On-Hook nailups comes into play. On-Hook allow the agent to hangup their phone device and it will then ring when a new call comes into the queue. Which makes it better for cases where there are breaks between calls or other tasks to do.
This gives us the two primary approaches for nailups, which are On-Hook and Off-Hook. How does an agent get linked into the system to do these? Traditionally we would see a local extension device directly connected to the ACD System as the nailup target. So this extension would function as described above for either On-Hook or Off-Hook. However there are more flexible alternatives as not everyone is able to be local.
- VoIP extensions. These would appear like any other extensions but a user would have a VoIP device (Smart Phone, Hard Phone, Soft Phone) almost anywhere they want to work. This requires a decent internet connection and a secure way to connecting to the system. Once connected the VoIP extension should appear and function as any of the local extension devices.
- Call Out/External. This feature allows the admins or agent to provide a phone number to call the agent. This mode can work for both Off-Hook and On-Hook. With On-Hook one does need to consider the delay to ring an outside phone, as sometimes this will add a second or two before the agent will hear the ringing and answer the call.
- Call In. This feature would use a DID and IVR which the agent would call into and once they entered the authentication info a valid nailup would be established. This mode works for Off-Hook as the agent is the person to initiate the connection and needs to keep this connection up while they are working.
Influence of Asterisk on Cloud call center landscape
Cloud based managed service providers are rapidly growing. The most recent financial statements from inContact and Interactive Intelligence point to this trend. Most call center software vendors are making a concerted effort to move from selling hardware and software as a product to selling an on-demand service. This move is being thrust upon them by the rapid change in networking and infrastructure. But the biggest threat to their survival comes from technology companies that leverage Asterisk and other open source elements for the technology stack.
Continue reading “Influence of Asterisk on Cloud call center landscape”
Virtualization Issues to Watch For With Your Call Center Software
The modern call center has benefited greatly from improvements in virtualization technology, and the widespread acceptance of the cloud contact center as a wise choice has accelerated improvements in that field. Asterisk runs well on both actual and virtual commodity servers and has done for several years now. Continue reading “Virtualization Issues to Watch For With Your Call Center Software”