don't have stats on it but off the top of my head, it would be:
1. product requirements / live qa / ux
2. engineering questions and discussions
3. context transfer from a customer requirement
don't get me wrong, slack sucks for a lot of things, which is why we're fans of @saradu.
@WorldofAnshul truthfully though, our main method of 'selectiveness' is now hopping on huddles. so, transcripts. those 'selective' channels aren't super impactful.
so, all channels have agents, and they are free to jump in whenever.
we used to do team channels for alignment (agents read-only), but that actually got super annoying.
rather, what we have now is 'selective' channels. agents can still jump in and chime (e.g., product decision being made would negatively impact a specific client), but they are forced to conform to a specific style.
i think 'slop' or agents chiming was an issue at the beginning of slack agents. we fed it instances where we thought it should/shouldn't jump in/preferences on answer length. kinda like how you expect a junior to pick up the culture after a few weeks.
still iterating on it, but, our team has shifted pretty much all our engineering from local agents to slack.
you get other insane added benefits too. the biggest one being filtering poor context dumps as a result of mcps.
as an example, you want an agent to go through a feature that a specific client wanted. it'll pull the relevant context it has from linear, transcripts, emails, and if it has any questions, will ping the relationship owner and the product owner. at the beginning, it was annoying. after enough iteration, we're at a point where we couldn't work without it.
we have a channel for each of the various projects, clients, etc.
we trigger everything on slack, and it reports back to us on slack. we have multiplayer communication there too, so multiple people chime in.
the cool thing is that everyone sees everything, and that people have agents that will ping them/dm them when people work on overlapping areas or where the person can give context.
@gabriel1 the most helpful advice ive ever been given for enterprise scaling is that top of funnel fixes all problems
having sheer numbers help you identify the type of customers that require less work to close, and the reasons why that is the case
@saradu calling out a perfectly supportive thing for a partner to do because of “patronage network” or “journalism” is so parasocial. this is actually a great example of why the rest of the world thinks SF is weird
ogs know sara has been inspiring the ecosystem for 7+ years