We have one calling queue attached to an auto attendant for our company's main phone number. Our receptionist attempts to pick up calls using the Teams desktop client on Windows 10, but it often takes several seconds before the call is connected. Sometimes when attempting to answer, the caller only hears clicking and the receptionist is still unable to answer.

Calls put on hold are sometimes unable to be picked back up without 30 seconds passing by.

This is all with Domestic Calling Plan in the United States. I don't know how much more "vanilla" our environment could be, but this performance is inadequate.

We're running a webinar using Teams Live Event. The content queue doesn't work, you can't queue content only share one person's screen at a time.

If another user shares their screen it immediately overwrites the content being broadcast, which is not good at all!

We expect better controls. Why are producers being broadcasters as if they're presenters and not have the option of talking into presenter's ears without being broadcast? Why can't presenters have producer controls if we want them to? Why can't presenters be changed to producers on the fly? Why does a powerpoint not tie in properly with the broadcast controls? As in why can't we show presenters what the next slide will be if it's not their presentation?

It's got a lot of potential but it's a pretty basic at the moment.

For Canadian callers, the outgoing name display does not currently work. When I make an outgoing phone call via MS Teams, the call recipient only sees my business number. They do not see my company name or any name associated with that number. In the US, there is a CNAME database that needs to be updated with a name for each phone number. In Canada, there is no database. The caller's phone company sends the caller's name, whether it is VoIP or traditional phone. Please, MS Teams, add a feature where Canadian customers can indicate what business name should appear on a call recipient's phone. Without this, customers might think I am a spam call if they don't have my phone number saved in their phone.

I got an email with an issue regarding 2 of my 3 port orders. I send an email to the ptn@microsoft.com address and I have received NO CORRESPONDENCE from them. I've opened a ticket with general support who has no clue and all they did was forward the ticket to the PTN email address. Every other phone service on earth has a tech support department you can communicate with via phone or trouble ticket but Microsoft's PTN department has a dead-end email address with NO RESPONSE, TROUBLE TICKET or way to get resolution on a time sensitive transaction (moving live business phone numbers.)

Does anyone at Microsoft care????? i don't think so.

In Skype for Business, any and all telephone numbers published in AD (i.e. main / primary "telephoneNumber", "mobile", "homePhone", "otherTelephone" etc.) would appear in a drop-down menu (along with the default "Skype for Business call") any time there was a call button, either from the buddy list or from the contact card.

In Teams, this is quite broken:

1 Phone numbers visible in the contact card in Teams are not diallable / hyperlinked.

2 The Call button from the contact card presents a different user experience to the Call button in the chat screen. In the chat screen, it provides "Teams call" and the "mobile" phone number field (if populated in AD) in the drop-down menu as options. In the contact card, it just defaults to "Teams call" without giving you any option to dial alternate published numbers for the user.

3 The drop-down menu behind the Call button should display any and all telephone number fields published in AD, not just the "mobile" phone number field. Understand the need to push a "Teams call" as a preferred option, but there are legitimate customer scenarios where a Teams call is not possible, and click-to-dial to other published telephone numbers for the contact is required.

Using Microsoft Teams & CloudPBX with AA and Call Queues.

If a user that is part of a call queue is actively making an outbound PSTN call (call not connected yet), and a call comes into the call queue, the outbound call is put on hold, and the inbound call is automatically answered, without the user actually clicking the answer button. The outbound caller hears nothing (because they are on hold.) We thought the fix would be to set the toggle on the call queue for "Agents can opt out of taking calls" but that didn't work. I have an existing case with Microsoft for this, with no resolution after a month.