Busy on Busy - Conference calls

%3CLINGO-SUB%20id%3D%22lingo-sub-1794441%22%20slang%3D%22en-US%22%3EBusy%20on%20Busy%20-%20Conference%20calls%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1794441%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20guys%2C%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20want%20to%20make%20sure%20this%20is%20not%20just%20a%20%22problem%22%20in%20my%20tenant.%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20enabled%20busy%20on%20busy%20-%20because%20if%20someone%20is%20on%20a%20call%2C%20you%20should%20not%20get%20again%20a%20call%20automatically.%20Which%20is%20a%20very%20bad%20user%20experience.%20So%20far%20-%20so%20good%20%3A)%3C%2Fimg%3E%20but%20if%20you%20are%20on%20a%20call%20and%20someone%20wants%20to%20add%20you%20to%20a%20conference%2C%20you%20will%20get%20also%20a%20call%20although%20you%20are%20already%20on%20a%20call.%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20not%20cool%20-%20for%20me%20it%20is%20ok%20when%20you%20get%20something%20like%20a%20call%20waiting%2C%20but%20when%20the%20user%20is%20getting%20annoyed%20by%20a%20additional%20call%2C%20that%20make%20no%20sense%20in%20my%20point%20of%20view.%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20this%20the%20expected%20behavior%3F%20If%20yes%2C%20this%20should%20be%20fixed!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1794441%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECommunity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EConversations%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Contributor

Hey guys, 

I just want to make sure this is not just a "problem" in my tenant. 

We have enabled busy on busy - because if someone is on a call, you should not get again a call automatically. Which is a very bad user experience. So far - so good :) but if you are on a call and someone wants to add you to a conference, you will get also a call although you are already on a call. 

This is not cool - for me it is ok when you get something like a call waiting, but when the user is getting annoyed by a additional call, that make no sense in my point of view. 

Is this the expected behavior? If yes, this should be fixed! 

0 Replies