 Jessica says, my company using Microsoft Teams primarily for the chat app. It's getting difficult to separate the chats based on which client we are discussing, and the crosstalk is overwhelming. I would like to move us over to using the Teams app, would love feedback on the best way to set this up. Create a separate team for each client, create one team for clients, and add a channel for each client. Also, is there a way, if that's some indication, Jessica, that we all shook our heads now? Also, is there a way to bump up the notifications? When a new team chat is made, the only alert we get is a little red dot on the activity app, but not on the Teams app, which is weird. How can we make Teams app notifications better? I'm chomping at the bit right now. Do I? So many things. Who needs to work together? What are they working on and how are they getting their work done? The team is who needs to work together, the channels are what are they working on, and the tabs across the top of what tools are they going to use to get their work done. I can see the reason for having clients and then having a channel for each, if there's not a lot of activity or their potential clients, and eventually they grow up and become their own team, but who needs to work together because they will desensitize to all of that banter and shut it down like they do email. Because everybody's ignoring their email now. You don't want that to happen. Let people focus on what they need to focus on. I mean, like a lot of us, I went right out when Teams was brand new and I was consulting independently. I went and created, again, just for me internally I had one client team created a channel for each one. Then I had five or six clients and then one said, well, I'd really like to be able to collaborate with you around all these things, and realized, well, I can't invite you to this because then you would see every other client. So the way that we do it now today, and I'd love to hear from all of you, but is that we have different teams for each client? Absolutely. Also, if you try to pigeonhole everything into the same team, that means everything you're doing for that one client that only gets one channel, you're going to have to do nested folders in that files tab, and the deeper that nested folder gets, the worse your search results are going to be, the slower your indexing is, the slower your load time is, it's just a bad experience. If I wanted to talk to Sharon about the migration of Sherry's content, I'm doing that. Again, it's like chat in one pane where we're also talking about helping Sherry with her Power Pages and all the other things. You can't organize your content, your conversation if you're cramming it all into the same thing. So concur one team per client. Yes, Sharon, I had my hand up, but it didn't work. I've got my client too small. I didn't see it. Sorry about that. Well, because the channels are, what are the topics around that client? If you're talking about financials, you have a different channel per project that you're working on. So then as certain projects are finished and other ones light up, you can hide the channels that you're not working in anymore. But if you have one projects channel, then like you're saying, now they're all mushed together and you can't focus in on what's important and for you. So I understand the desire to have a single customer or client team. It's compartmentalized and it really makes that left navigation pane clean. But where it falls over is you can only have so many channels in a team. So you could theoretically run out. It was 250 at one point. It's up to like 1,000 now. Yeah, it's moving up to 1,000. So then you can only, even if there's 1,000, when that rolls out, you still can only show a certain amount of channels. So all of those channels that could be shown in a team now are hidden and now the people will have to manage their own channels to show what are hidden and what show by default. Which means you're going to run the risk of missing notifications. Well, that's not good because not everyone's going to know to like app mention you to make sure that bubbles up. So you get into all of these areas of limitations now. And so one team per unit of work or business identity, whatever, makes the most sense. Yes, your left navigation gets overwhelming. But you will not necessarily be involved in every project or maybe you have customers that you're no longer responsible for. Inside of teams, you have the high show option. You didn't remove yourself from the team. You didn't delete the team. You just said, like, I'm getting rid of the static because teams can be overwhelming, like very overwhelming with content and notifications. So if it's really important and I've hidden the team and they said, Norm, we need you app mention, boom, it goes up to the activity icon or whatever that thing's called in teams. And so now I know that the stuff that's important to me that I need to action is in that activity. So I don't have to do this hop-downs left to right view of everything that's happening in teams. I go after the priority items. So it's about limitations. It's also why for those organizations, Microsoft, who use teams for all the community pages, it doesn't work on people like me because, like, Norm, just you point out, if I'm never app mentioned, I will never go dig through all of those archives of all those channels, of all of those threads and conversations. It's just lost, you know, of all this great information that's out there and why, like, Viva Engage is a better platform for doing that kind of thing. But anyway, but yeah, there's a, I was just gonna, something that Joy and I can both talk about is the importance of going and, again, pre-provisioning, like, setting up the templates for it. You might have a template for a team site for a customer or for a partner that they're structured the same. So while you have the freedom to go and add on to that and extend it and do the things which are unique to each of those customers or each of those partners, if there's a standard way, so we know every team that is partner-related or customer-related has, you know, a project management channel, has a, you know, it has the calendar, of course, has certain tabs, has certain third-party tools. Maybe all of them have a unified access if you have, like, a project management organization that's, like, a centralized forms repository, which you can link to within each one of those as part of that provisioning template. So there are ways that you can streamline the creation of those teams, but it does come back to having those, you know, those new teams. And as you implement that consistency within the teams, you start to reinforce the consistency in which the business works, you then start to build these efficiencies for the people doing the work. And I don't know if anyone said it, just maybe because we're taking it for granted, but for the user who posed the question, Jessica, make sure that that chat moves over to a channel conversation. So when you're talking about the context of a customer or a client, it happens in their respective space. So it has the context. It doesn't get lost in those long-running histories. So chat comes to a channel conversation and you will save your user so much frustration by doing that. Preach. That should be like a slogan for all the stickers. Don't chat, channel. Yes, get on that. You're the sticker king. You're the sticker king. But so by doing that too, you're making sure that everyone that's on the team, working with that client, is in the loop for the conversations going on that they need to know about. And Jessica too, to answer your questions about the activity, if you app mention the channel, that pop up on the desktop or whatever, we'll have the channel name and give context, the notification. A badge will go on the team. If you app mention the whole team, right? You'll see that the team, the comment was made in the team, it won't have like the topic specific there. But the badge will go to the team if you use your app mentions. You can also control your own, each person can also control their own notifications on each channel, boost them themselves so that they get emails or banners or whatever for that activity too. But there is kind of a, there's a smart way to create content. App mention people, app mention the teams, use- Channels. Hashtags, use channels for the conversations. Subjects in the conversations. Yep. Bad subjects. Yep. Now, now we're just getting crazy. And if you're gonna be having- Right with MLA standards. If you're gonna be busting out, it's like single channels into one team or you know you're gonna be creating multiple teams. You need to be creating multiple teams. Naming conventions matter. Mm-hmm. And I'll just leave that there. Hashtag governance. Like that.