I have the situation where Direct Routing calls come through to Teams agents regardless of what their status is set to
Here's the scenario. I have the same agents handling calls for 3 companies, so they need to know which inbound line is calling in order to answer it with the correct "company message". They work different shifts, but need to use Teams even when they are not on shift to take calls.
The problem is that when they are off work or not scheduled to take external calls and set their status to Busy/Away the calls still comes through. They have to fully log out of Teams which is not ideal as we use the platform for internal comms also.
The ideal configuration for this is that the Auto Attendants and Call Queues are all managed externally with the telecoms company/SBC via a Sip Trunk Call Manager (STCM), and the call is finally put through to the agent(s) direct number in Teams. This is better for us, as the call flow is complex with multiple layers of AA and announcements etc and the STCM has some great features and reporting.
Is there a way to force this status back to the STCM, or even just give a 'busy' tone so that the STCM tries the next agent in the pool?
My work around so far is that the STCM manages the AAs for each inbound number, and then passes the calls onto a Ms Teams Call Queue - there is a separate call queue for each company/inbound number so that the agents can see what's ringing.
This gets over the Agent Status issue
I loose the call trace and reporting, as the STCM just sees every call and answered by the Ms Teams Call Queue.
I also can't seem to find much information on how multiple call queues are managed in Teams when they all go to the same agents. I.e. are they balanced or does one call queue take priority over the others.
There seems to be no way to report on Call Queue volume - how many callers are in each queue at any one time, queue time etc