Terry

My feedback

  1. 3,625 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    714 comments  ·  Public » People  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Terry commented  · 

    This is a no brainer, but lately, I've come across many requests/uservoices that seem obvious but are ignored by MS. It feels like once every 6 months, they randomly pick 1 of these to look at.

    Terry supported this idea  · 
  2. 686 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    163 comments  ·  Public » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Terry commented  · 

    Dear Microsoft: these issues are what made us choose another platform for our telephone needs. This living product breaks every 2-3 months with issues that are taking months or even years to fix. It's nice to see new features (5 minute warning before a meeting ends), but I'd rather see the basics work instead of nifty additions.

    After 3 months: our people are still unable to work on a citrix/terminal server because they cannot answer calls.

    Why hasn't this been acknowledged yet?

    An error occurred while saving the comment
    Terry commented  · 

    I noticed the exact same behavior as many people described as well. RDP'ing into servers for maintenance or troubleshooting. When a call comes in, you're haunted by the ring tone, unable to pickup. Why does a tool like MS Teams only rely on a toast notification, is beyond comprehension. You'd think that in the development of the tool, you'd first make it possible to have a call screen appear within the tool and get that to work, before progressing to the notication window.

    Terry supported this idea  · 
  3. 63 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    29 comments  ·  Bug Reports » Client - Desktop  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
  4. 61 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Bug Reports » Client - Desktop  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Terry commented  · 
  5. 248 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Bug Reports » Presence  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Terry commented  · 

    There's a larger thread handling away status, maybe the threads can be combined to create a bigger on: https://microsoftteams.uservoice.com/forums/908686-bug-reports/suggestions/41278342-teams-now-setting-my-status-to-away-after-10-min

  6. 96 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Bug Reports » Calls  ·  Flag idea as inappropriate…  ·  Admin →
    Terry supported this idea  · 
    An error occurred while saving the comment
    Terry commented  · 

    It feels like the people developing teams don't work with the product. The new meeting experience is one thing, but having multiple windows for 1 call results in poor user experience, especially when the windows don't stack like you would expect.
    This makes a basic feature (transferring) extra hard for normal users and end up in them just passing along phones or headsets.

  7. 2,441 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    259 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your continued feedback. We are continuously improving the clients to use less memory and RAM.

    The upgrade to Electron 10 has rolled out fully to the public at this point. Telemetry and testing has shown that this is helping to improve memory performance on the client.

    We will continue to work on improvements, and will share more updates as they become available.

    For more details on how Teams currently uses memory, please visit https://docs.microsoft.com/en-us/microsoftteams/teams-memory-usage-perf.

    Terry supported this idea  · 
  8. 2,156 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    392 comments  ·  Bug Reports » Teams & Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Terry supported this idea  · 
  9. 967 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    307 comments  ·  Public » Devices (Headphones, Cameras)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Terry commented  · 

    Nice surprise to come back from a few days off work and seeing teams updated on 24th september, and my headset RCC worked again. Hoping he next update won't break it again.

    Terry supported this idea  · 
    An error occurred while saving the comment
    Terry commented  · 

    For the sake of data collection, I'll add our setups:

    Windows: ranging from 1903 to 2004
    Headset: Engage 65, latest firmware
    Teams: 1.3.00.21759

    First mention of problems started at the beginning of September, have been testing several setups/options for the past 2 weeks.
    All RCC functions are affected (pickup, vol up/down, ...), there's no communication between teams and the headset.
    We can still answer the call through the softbuttons and afterwards activating the headset with the pickup button.

  10. 44 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Bug Reports » Calls  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Terry commented  · 

    Just had a support call, saying they are aware of the issue and are tracking it in roadmap ID 57294 (see admin center of the tenant).
    Disabling the experience in the team clients is still their go to workaround, which I have yet to confirm it works, as the issue doesn't happen on all incoming calls.

    Terry supported this idea  · 
  11. 286 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    65 comments  ·  Public » IP Phones  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Terry commented  · 

    We're halfway through Q2 of 2020, we're also still experiencing this issue. We solely use the teams clients to operate our voice lines. We cannot keep count of the number of calls ended because of the no response after pickup. Annoying internally, but a dealbreaker when used in a sales perspective. If only we had more feedback on how this issue is being handled.

    Terry supported this idea  · 
  12. 22,702 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1401 comments  ·  Public » Calendar  ·  Flag idea as inappropriate…  ·  Admin →
    Terry supported this idea  · 

Feedback and Knowledge Base