Forum Discussion
'Call Waiting' notification
There's a few threads discussing 'Busy on Busy' (BoB) but I can't find any discussing the terrible user experience when BoB is disabled. With a traditional telephony solution where 'Call Waiting' is...
I’d like to revive this topic to see if any progress is being made on a practical Call Waiting solution in Teams.
Peter_Joseph I suggest upvoting this Feedback if you haven't already: https://feedbackportal.microsoft.com/feedback/idea/7cfe0515-272e-ec11-b6e6-00224827bbc2
- Done! Thanks. I'm frankly surprised this hasn't garnered more than the few complaints here and at the topic you referenced above.
- Hey, friends, the latest Teams update finally addresses busy on busy with some additional features that we've been waiting for. Now you have options both in the TAC and on the desktop app depending on how you want to control it. And it actually works based on whether the user is on the phone and not also based on busy status in calendars as presence-based routing on call queues does. It's still not a full blown call waiting experience, but this goes a long way to easing end user frustrations and is a major win for Microsoft and us!
Thank you for the update, is there an announcement or blog post that describes the new features?
- Hi Ryan, I'm not sure the topic you mention is the same issue. What I'm asking for is simply the option to provide busy tone to a caller when a called number is busy. It's a basic telephony feature that Microsoft appears to not understand.
Stewart_Ross You may want to re-read your original post as you are specifically referring to "that loud, obtrusive ring tone [that] blasts over the existing call", which is exactly what the linked Feedback item refers to.
It is possible to have a caller receive a busy signal by assigning a Calling Policy with the "https://learn.microsoft.com/en-us/MicrosoftTeams/teams-calling-policy#busy-on-busy-when-in-a-call" option configured.
- My apologies but my general frustration with Teams telephony got the better of me... 😉
My main concern is that calls to services with Busy on Busy activated that do not have a call forward no answer destination set fail when the service is already active on a call. The caller should get busy tone under those circumstances. Some users don't want a call forward no answer destination set.
