Changes in Creating SfB Call Queues and Auto-Attendants

%3CLINGO-SUB%20id%3D%22lingo-sub-390520%22%20slang%3D%22en-US%22%3EChanges%20in%20Creating%20SfB%20Call%20Queues%20and%20Auto-Attendants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390520%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20I%20notice%20that%20the%20ability%20to%20create%20call%20queues%20has%20moved%20from%20the%20older%20SfB%20Admin%20legacy%20portal%20to%20the%20newer%20teams%20portal.%20There%20has%20been%20some%20changes%20to%20the%20help%20guides%20but%20they%20don't%20seem%20to%20match%20up.%20I%20cannot%20select%20a%20Service%20Number%20to%20tie%20the%20call%20queue%20as%20I%20could%20previously%20-%20instead%20this%20appears%20to%20be%20replaced%20by%20adding%20a%20'Resource%20Account'%20but%20I%20cant%20seem%20to%20finds%20exactly%20what%20that%20means.%20I%20cant%20search%20on%20any%20of%20our%20Service%20numbers%20(we%20had%20quite%20a%20few%20spare)%20do%20they%20require%20some%20sort%20of%20migration%20to%20be%20able%20to%20be%20seen%20by%20the%20Teams%20Admin%20portal%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20do%20see%20in%20a%20screenshot%20under%20'Distribution%20Methods'%20that%20Round%20Robin%20routing%20has%20been%20added%20-%20this%20is%20excellent%20news%20-%20but%20how%20do%20I%20actually%20create%20the%20Call%20Queue%20now%20without%20being%20able%20to%20select%20the%20service%20number%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERefer%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-US%2Fskypeforbusiness%2Fwhat-is-phone-system-in-office-365%2Fcreate-a-phone-system-call-queue%3FWT.mc_id%3DTeamsAdminCenterCSH%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-US%2Fskypeforbusiness%2Fwhat-is-phone-system-in-office-365%2Fcreate-a-phone-system-call-queue%3FWT.mc_id%3DTeamsAdminCenterCSH%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-390520%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHow-to%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-506902%22%20slang%3D%22en-US%22%3ERe%3A%20Changes%20in%20Creating%20SfB%20Call%20Queues%20and%20Auto-Attendants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-506902%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20case%20anyone%20ends%20up%20here%20-%20the%20Legacy%20to%20Teams%20portal%20migration%20was%20a%20huge%20SNAFU%20and%20was%20eventually%20reversed%20by%20MS%20to%20the%20original%20state.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-506962%22%20slang%3D%22en-US%22%3ERE%3A%20Changes%20in%20Creating%20SfB%20Call%20Queues%20and%20Auto-Attendants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-506962%22%20slang%3D%22en-US%22%3EIt%20has%20been%20a%20huge%20mess.%20We%20discovered%20this%20when%20we%20were%20transitioning%20an%20office%20over%20to%20Skype%20for%20Business.%20Unfortunately%2C%20the%20port%20of%20the%20main%20office%20number%20went%20through%20and%20we%20were%20stuck%20not%20being%20able%20to%20assign%20that%20number%20to%20an%20Auto%20Attendant%20or%20Call%20Queue.%20Basically%2C%20our%20phones%20were%20down%20for%203%20business%20days%20%2B%202%20weekend%20days.%20When%20our%20customers%20called%2C%20they%20got%20a%20messaged%20that%20the%20line%20was%20disconnected.%20Microsoft%20Support%20provided%20absolutely%20NO%20help.%20We%20finally%20were%20able%20to%20port%20that%20number%20over%20to%20a%20User%20number%20which%20we%20just%20assigned%20to%20one%20user%20to%20handle%20the%20calls%20for%20the%20last%202%20weeks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-522005%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Changes%20in%20Creating%20SfB%20Call%20Queues%20and%20Auto-Attendants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-522005%22%20slang%3D%22en-US%22%3E%3CP%3EAnd%20today%20they%20have%20re-implemented%20the%20change%2C%20and%20fingers%20crossed%20it%20looks%20to%20have%20been%20more%20successful%2C%20our%20agents%20still%20receiving%20calls.%20There%20are%20double%20ups%20of%20queues%20visible%20in%20the%20Agents%20call%20queue%20profile%20screen%2C%20but%20calls%20are%20being%20delivered%20to%20Skype%20rather%20than%20Teams%20like%20last%20time.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Today I notice that the ability to create call queues has moved from the older SfB Admin legacy portal to the newer teams portal. There has been some changes to the help guides but they don't seem to match up. I cannot select a Service Number to tie the call queue as I could previously - instead this appears to be replaced by adding a 'Resource Account' but I cant seem to finds exactly what that means. I cant search on any of our Service numbers (we had quite a few spare) do they require some sort of migration to be able to be seen by the Teams Admin portal?

 

I do see in a screenshot under 'Distribution Methods' that Round Robin routing has been added - this is excellent news - but how do I actually create the Call Queue now without being able to select the service number?

 

Refer https://docs.microsoft.com/en-US/skypeforbusiness/what-is-phone-system-in-office-365/create-a-phone-...

3 Replies
Highlighted

In case anyone ends up here - the Legacy to Teams portal migration was a huge SNAFU and was eventually reversed by MS to the original state. 

Highlighted
It has been a huge mess. We discovered this when we were transitioning an office over to Skype for Business. Unfortunately, the port of the main office number went through and we were stuck not being able to assign that number to an Auto Attendant or Call Queue. Basically, our phones were down for 3 business days + 2 weekend days. When our customers called, they got a messaged that the line was disconnected. Microsoft Support provided absolutely NO help. We finally were able to port that number over to a User number which we just assigned to one user to handle the calls for the last 2 weeks.
Highlighted

And today they have re-implemented the change, and fingers crossed it looks to have been more successful, our agents still receiving calls. There are double ups of queues visible in the Agents call queue profile screen, but calls are being delivered to Skype rather than Teams like last time.