Enhanced Call Queues
When will Serial Routing call queues be enhanced? Currently the routing is based on the alphabetical structure of the distribution list which does not work for my call groups. We need the ability to define the routing by agent.
Lenny Wolf commented
I think the Serial Routing option is ment for when you select "Chose users and groups" and not a team. When you select "Chose users and groups" you can change the order there and it will apply to the Teams Client.
Stewart Nicholson commented
This is a great idea, I'd even go as far as saying essential as we have a number of clients that want to use serial routing but need the routing to use a specific order.
Jenifer C commented
I find this very important to the call queues
YES! this would be a great help
We are about to implement Microsoft Call Queues. Serial routing will be our most preferred option and yet there is no way of consistently ordering the agents in a Call Queue. How can Microsoft have a routing option that cannot be used if you can't decide the ordering of your agents? This seems like a bug to me and not a feature request? Would help us a lot if this could be sorted quickly!
Ditto to everyone else's comments. Need to be able to set an order for the agent list.
Please add this feature to match the actual description the serial routing option displays : "When serial routing is used, incoming calls will ring call agents one by one, starting from the beginning of the call agent list."
Serial Routing is a fundamental function in any call queue system, whereby you can select the order in which agents are called based on priority. please give us this feature Microsoft
This is so important! I will concede that Microsoft seem to be working ******* Microsoft Phone System, and a lot of issues are slowly getting resolved. We currently have Serial Routing using a 365 group configured and working well, however we are wanting to desperately implement the new "Voice enabled channels" feature for call queues, specifically to take advantage of the new Caller ID function that allows agents to "call as" the Call Queue number (which is HUGE!). However when we configure this, we loose the option to use serial routing. Specifically, we can still select the Serial routing option, but loose the ability to order the agents as it is using Team membership. C'mon MS, you're so close!
When using a Team for Call Answering, and selecting the Routing Method = Serial Routing, the application clearly states "When serial routing is used, incoming calls will ring call agents one by one, starting from the beginning of the call agent list."
It says nothing about that it will ring in alphabetical order. In fact, there is no "Call Agent List" that exists anywhere. Therefore, this is a bug (not an enhancement or feature request) as the application clearly states the way it should work, but yet does not have the feature with which to set an order.
Serial Routing is a fundamental function in any call queue system, whereby you can select the order in which agents are called based on priority.
Richard Bradley commented
Answering groups are a great idea as the group membership can be devolved to one or more group owners. However, ringing everyone at the same time is not viable for our environment.
In order to get the linear approach we need (a defined order - not alphabetic) it will be necessary to define named agents in the call queue. There is no way Teams administration can be devolved to group administrators so they can just alter the membership and order for their own call flow. This leaves us with a cumbersome support overhead.
Joe Hendricks commented
Not sure if there is a perm fix for this, however, I noticed a change in our tenant where you can set multiple Call Groups(Distro groups) in a call queue. The work around I have been using is if the call queue has 5 users, I make 5 distro groups and order the distro groups in the call queue. It's not ideal but it's a band-aid until Microsoft enables this feature that has been around since the beginning of time.
This should be a no brainer. Serial routing is useless without the ability to order the list of people in a group.
MS saysfor Serial Routing: "want skip agents who are offline, have set their presence to Do not Disturb, or have opted out of getting calls from this queue."
That is completely inadequate! Callers coming through a call queue (central phone number) are offered to agents who can not answer the phone at all, as they e.g. are in break or in a meeting. Only after the defined expiry time (at least 15 seconds, about 3x ringing), the caller is offered to the next agent, which may not be available too. This creates very long and annoying waiting times for the caller. Currently, the only way to quickly accept a caller is to put routing on "attendant", where all the agents ring at the same time. An absolute horror for employees! When a call comes in, it rings immediately ANYWHERE!
One of the big issues we have with further adoption of Teams is the poor support for auto attendant, group numbers and call routing. I have had to set up an an instance of Asterisk to front group numbers for routing, and it seems others are taking up similar services from their Telco providers to overcome these issues. These are features that other platforms have had forever and it shouldn't be necessary to insert an intermediate system to overcome such basic inadequacies.
As a footnote, any enhanced functionality needs to be manageable with a GUI as this is something we'd delegate to non-technical admin staff who wouldn't be proficient with powershell.
Tyrel Alastair Hunter commented
This is needed for sure, but so are better auto attendant(s).
Steven Jack commented
I agree with the comments made here, we also make use of visual indication of a hunt group call where users in the group are not in the same location
Dave Franklin commented
We are in the market for a new phone system and a vital part of that system will be the use of Hunt Groups, Group Pickup, Extension Pickup and so forth which are functions our current Siemens ISDX(L) has. Any lack of these "basic" functions would be a show stopper for our considerations and for most institutions looking to replace a system with Teams. This does have the opportunity for Microsoft to get a good foothold in the telephony market within HE and other institutions if it is delivered as a fully working replacement phone system.
Peter Hurst commented
We are investigating teams for our university, however hunt groups are key to an enterprise scale deployment to our 3000 staff (about 10-20% would be part of hunt groups. At present the lack of a one stop shop for telephony would prevent use looking at Teams telephony. If MS are serious about this they either need to encompass the core telephony functions or improve integration with third party suppliers like cisco and mitel.
Peter Kent (Jisc, UK) commented
I'm leading a Teams for telephony pilot in the UK, and provide weekly updates to 51 universities and research organisations around the world. If it wasn't for the lack of call queue group functionality we'd likely have implemented - if the features can't be provided, can APIs to allow third party integrations to work?
The key requirements here are to have hunt groups which are capable of:
- Ringing all members of a group at once (which Teams can do).
- Ringing members of a group in a range of serial models:
--- Ring members in a strict pre-determined order (taking in account anyone who’s opted out of the group).
--- Ring members in a random order.
--- Ring members in an most-idle order - whereby the first person to get the call is that person who has been longest off the phone or hasn’t picked up a call for the longest period.
- Escalating calls through groups. For example, a call comes to one group and doesn’t get answered so moves to another group. Where we’ve used this is a our service desk where engineers phones ring all at once, if no one picks up it’ll ring a broader group (the original group plus senior engineers).
- Allowing members of the group to easily opt out of receiving calls to the group - when they’re on lunch, not on duty, etc.