Hi there, you’ve reached the user feedback site for Microsoft Teams. It’s managed by our Customer Advocacy Team inside Microsoft Teams Engineering led by Karuana Gatimu. Our entire team believes in representing your needs inside our engineering group and we appreciate the time you take to share them with us. Rest assured that a large team of dedicated people read and discuss your feedback!

Here’s how to get your voice heard:
1 — VOTE for existing ideas (this will also subscribe you to the idea’s status updates)
2 — SUBMIT new ideas (Please include only one suggestion per post. Duplicates are merged together.)
3 — RATE the product by clicking the little orange star on this page. This helps us understand our overall standing with users. It will collect your rating every six weeks.
4 — COMMENT in ideas’ threads, which we check regularly

For official product and feature updates we recommend three things:

Stay tuned here: We update our work items monthly
Read our Blog: Official announcements come from our blog at
Review the Roadmap: Our upcoming features can be seen within the Microsoft 365 roadmap site at

Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more
The Fine Print:  We have partnered with UserVoice, third-party service and your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including license terms. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.   

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Use shifts to allocate roles and responsibility - i.e allocate an alias

    All the specification of a role/responsibility for each shift that can then be use to identify or @ a user.
    For example lets say I assigned an on-call shift '8pm-8am as 1st floor on-call' then I gain the alias @first-floor-on-call for the duration of the shift so someone can @GeorgeHarvey or @first-floor-on-call, both will come to me, except when my shift ends @first-floor-on-call is then forwarded to the next user, and they can see any outstanding tasks/messages due for @first-floor-on-call

    5 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

    4 comments  ·  Shifts  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the feedback. My name is Amir and I am a product manager in the Shifts team. Can you please explain a bit more about this scenario? I am trying to understand what is applicable for the Shifts app vs. general group/1:1/channel chat. Thank you!

    You are receiving this email because you agreed to be contacted by Microsoft about your product feedback
    Privacy Statement
    Microsoft Corporation, One Microsoft Way, Redmond, WA 98052 USA

  • Don't see your idea?

Feedback and Knowledge Base