Forum Discussion
Chief Exec / Senior Manager --> PA call group
TheGarrison What are you using for Teams PSTN connectivity? Do you have Direct Routing with control over the SBC appliances? A solution may be achievable if so. If you don't have ownership of the SBC(s) or are on Calling Plans etc. then less so, but perhaps still achievable.
My immediate thought would be to put the CEO's non-private number on an Auto Attendant which has the same business hours as your legacy workflow and assign the existing private number as the CEO's Teams number. Create a Call Queue that contains the PA's. During working hours calls to the CEO non-private number will be routed to the PA Call Queue, and they can transfer calls by name or number to the CEO. During out of business hours you can configure the Auto Attendant to route to the CEO by name or number.
The problem is caused by virtue of the fact your existing solution needs the CEO to have 2 numbers. This can't be achieved, so you need to move one of those numbers - in this case to an Auto Attendant that will then allow you to retain similar functionality.
Would that work?
Also, is this just for a single CEO, or a configuration that needs to work for a number of C-Level persons?
Hi, we are on Direct routing and have access to sip trunk call manager.
The scenario you mention above moving the number from the CEO over to the hunt group only really addresses external calls, user that are inside the organisation don't dial a DDI, they locate the person via the directory and then call them, and if 6pm at night will honour the blanket forward and will never get to said manager. he call queue addresses the problem as we can use the auto attendant but it doesnt help as the out of hours destination would need to be the CEO but user is on a blanket forward to delegates...
I had thought of puting in a call queue yes and it almost fits the bill but as we cant assign the private lines it breaks down during the out of hours window because the CEO would have the blanket forward all calls to the Call queue.
Unless im missing something...
Ideally, we would want to roll this out to around 7-8 people as we did in the SfB world. Seems a simple thing to address from a MS end, why don't they allow private lines anymore, or simply just allow to add a 2nd -PhoneNumber
TheGarrison Understood.
I think you could still work around it by virtue of the fact that call queues dont honour call forwarding (so could add the CEO account into a call queue to work around the blanket forward), and by having a scheduled task run the associated PowerShell for changing call forwarding settings on the account at the required business hours.
It would indeed be a bit messy, perhaps to the point where it's worth acknowledging the limitation in this area and setting new user expectations / behaviours.
I'll have hands on later so will have a further look rather than off the top of my head.