Thank you! 👍

Awesome, I'll add 'saving lives' to my resume 😀 You're welcome, glad it helped out!

Thank you! Glad you liked it!!

Glad you liked it!

Awesome, glad to hear that!

Glad you liked it!

Awesome, thank you!

Hi there! Part of this design is standard Microsoft Teams, ie, you have a Team, and the Team has channels. The idea here is we are 'voice enabling' the channels and tying them to the queue. In your case, I believe you'd create a Sales and Support Queue, and tie each queue to a channel. In each channel you'd have the agents corresponding to the queue. These could be the same people or different. Additionally agents can opt-in to receive calls or not. Hope this helps.

Hi @@CollaborationSimplified, I'm not sure as the channels need to be standard (and not private), and with a standard channel, you can't change the members (it takes all the members from the group). Unless I missed something?

Hi, I picked up the call using Teams. I believe Elon was logged in as the agent on Teams. You're most welcome!

Not yet - but stay tuned!

Hello, you can add up to 200 agents via a Teams channel. You must be a member of the team or the creator or owner of the channel to add a channel to the queue. Some more info here: learn.microsoft.com/en-us/microsoftteams/create-a-phone-system-call-queue?tabs=call-answering

Thank you, I'll add reporting to the list. Regarding 'hunt groups' - there is a serial routing mechanism: rings all call agents one by one in the order specified in the Call agents list. If an agent dismisses or doesn't pick up a call, the call will ring the next agent. This cycle repeats until the call is answered, times out, or the caller hangs up. There are other routing methods as well. You can find out more here: learn.microsoft.com/en-us/microsoftteams/create-a-phone-system-call-queue?tabs=agent-selection#step-4-select-your-agent-routing-options

Limitation will be on how many agents you can have in a channel - how large is your call center and how is it broken up?

@@CollaborationSimplified I tried adding 'private' channels but during the CQ creation, I could select the Auto Attendant team that I created, but none of the 'private' channels would show up in the channel drop down... only the 'standard' channles would show. Is this how it's supposed to work?

@@wmshanejones thanks for posting your question on the Google group! It'll help others find answers to similar issues 👍

It's not, I made it up to create the call center. You can call in to 949.313.8159 to test it out. Cool name huh? :)

Hi, that sounds like a smart approach. I haven't tried it but don't see why not. Let me know if it works out.

Please share how this resolved

You'll need to add a Teams Phone license - that will unlock the features you mentioned. learn.microsoft.com/en-us/microsoftteams/here-s-what-you-get-with-phone-system

I believe the closest we can come is this level of exception handling: learn.microsoft.com/en-us/microsoftteams/create-a-phone-system-call-queue?tabs=call-exception-handling#no-agents-optedlogged-in-set-how-to-handle-calls-when-no-agents-are-optedlogged-into-the-queue

Hello, can you post your question on your support group? Thank you groups.google.com/g/collaborationsimplified

Totally possible. You can nest auto attendants (aa). First aa lists the languages and then sends off to another aa that offers options.

@@CollaborationSimplified ok so it has to be different auto attendants cant create sub menus in one auto attendant right? Do you have a video on this by any chance?

@@CollaborationSimplified appreciate your prompt reply

You're welcome. Yes, my understanding is it's via a different aa. Fairly easy to do. You basically redirect the menu item to either an Operator, a call queue, another voice app, a number, voicemail, an announcement, etc. I can share a screenshot on our support group if you ask there.

@@CollaborationSimplified Thanks a lot I had an idea of doing this but just wasnt confident enough. I was able to make the sub menus out of it appreciate you