Thanks for visiting our forum, Microsoft Teams tag is mainly focused on the general issue of Microsoft Teams application troubleshooting.
If you're using macOS version 10.15 and above, follow the instructions at Use notifications on your Mac.
Also, regarding the stylistic issue of the notification sound, we recommend you create the feedback in Teams UserVoice. Many features of our current products are designed and upgraded based on customers’ feedback. With requirements like this increase, the problem may well be released in the future.
Thanks for your understanding and support!
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
I didn't say anything about the sound, that's actually had no design problems at all. I was talking about how the notifications are not OS native and behave weird -- they persist forever and remind me about events in the past, and they cover up other notifications because they are mysteriously not part of the OS notifications. Why would they sabatoge us.
I know I can send feedback, but I'm asking why they make decisions? How does a company work extra hard to make a more confusing chaotic experience when it will be almost no work to integrate with an existing framework?
Do you mean notifications will be delayed? To isolate if it's a client-side issue, try checking for the same issue in the Teams web client. In addition, we recommend you the following methods to solve:
No. I mean the notifications will remind me about a meeting that ended yesterday. And the notifications don't hide, you absolutely have to click on them. And they use their own proprietary notification system that sometimes blocks OS-level notifications. And then MS developers did extra work to intentionally ovrewrite native OS behavior to not use the built-in OS notification system that doesn't have the annoying design problems that they introduced for no logical reason.
I would honestly love to know why I need to know about a meeting that I attended that ended 20 hours ago, Teams is aware I attended the meeting, and it's still too dumb to realize the meeting ended 20 hours ago and that I didn't need the reminder after I attended it in the first place. Look I know MS doesn't have a QA phase after development which means it's generally just super buggy, but this is wildly stupid design.
I suspect this conversation is a microcosm of the dynamic between the devs and designers at MS. The designers try to guide the product and the developers are just confused and fix the wrong thing.
I'm trying to give design advice, but I keep getting completely arbitrary replies.
But yes, clearing the cache is a very common problem with the MS cloud infrastructure. The MS ecosystem has terrible cache management and everyone need to do this regularly just so we can see the same content in Teams, and that's only a fix 90% of the time. But this is not about the regular need for everyone to clear their cache like a poorly designed website.
For the issue, you could report a problem from Teams client here. Click Help >Give feedback. By pressing Send to Microsoft, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Thanks for your understanding!
Haven't received your message for a long time.
Do you have any further question on this topic now?
Sign in to comment