With the increase in popularity of Skype for Business Online Cloud PBX (as it is known for now…), I have been approached on many occasions and often presented with pushback, around the limitations of Cloud PBX Call Queues.
My first response is quite simple – they aren’t designed to replace an enterprise grade business contact centre. If we take a second to think about Server Response Groups – they were never aimed at replacing Enterprise Contact Centre, more so, bridge the gap to the requirement.
So, back to the point, with Cloud PBX Call Queues, I am often approached on their capabilities and limitations.
The main one being the fact that they are single tiered, so we call a given number, enter a given queue and a call is distributed to queue agents based upon Distribution lists:
Auto Attendants allow us to record custom business menu greetings/menu prompts that can then feed into a Cloud PBX Call Queue depending upon the key pressed. Auto attendants not only allow for transfers to call queues, but they also support the ability to transfer to another AA!
So, if we think about this for a second, we can record a customer business hours menu prompts (Press 1 for Sales, Press to for HR, press 3 for Marketing) that then transfers into either, another tier of options, or a given queue:
Based upon the above logic and call flow, we can introduce tiered call queues, providing callers with several options to find the queue best suited to handle their call.
The downside to this approach; each Cloud PBX Call queue requires a service number – they aren’t infinite either…hopefully we will support SIP only call queues soon!
Admittedly, it is still not providing feature parity when compared to a Contact Centre, but by using the above methodology, we can start to build out those ACD scenarios.