There are many out there who runs operator based switchboard in Teams. Back in the days you might had a Lync/Skype based switchboard or attendant. Since the has been some "delay" for Teams, you might end up with a operator solution.
This can be good but also a issure. You need to use your mobile to answer, and sometimes we see lack of integrations with Teams.
There can't be transferd or dial to a sipaddress based address. You need to transfer to a phonenumber.
Why not get a solution where the operator/agent can transfer to:
- sipaddress for the person
- to another queue
Then ofcourse you might also get AOUTH calendar integration, Teams presence, Mobile presence also if you need this and the Telco has this API.
For a few day's ago I got this in my LinkedIN feed. "Varberg kommun has done this."
I see for customers that are based in several countries with different telco operators, then you need one solutions for all countries. Then a third party hosted from Azure will be your path to get a switchboard - Attendant or a Contact Center solutions.
My advice is that when you run Teams with "Enterprise Voice", you are in the cloud, well then your Switchboard - Attendant should be in the cloud.