We've been using Fellow for about six months now to manage our team meetings, and the Slack integration is one of those features I have a real love-hate relationship with. On one hand, it's incredibly convenient to have meeting agendas and notes pop up right where the conversation is happening. On the other, my Slack channel can feel like it's being taken over by Fellow notifications.
The noise is real. I get a notification for:
* Every agenda shared before a meeting
* Every note or action item assigned to me during a meeting
* Reminders for upcoming meetings with pre-reads
* Follow-ups on overdue action items
For a smaller team, this might be fine, but with a dozen active projects, it can quickly bury other important messages.
That said, I've found it genuinely useful for accountability. Having action items from a meeting automatically posted into the relevant project channel means there's no "I didn't see the note" excuse. It creates a public record. We've also started using the integration to push decision logs from Fellow into a dedicated #decisions Slack channel, which has been a game-changer for keeping track of why we chose a certain vendor or path.
My current compromise has been to:
* Mute the direct @-mention notifications for agenda shares and reminders.
* Keep notifications for action items assigned to me turned on.
* Use dedicated channels for Fellow outputs (like #meeting-decisions) to contain the flow.
I'm curious how others have balanced this. Have you found a sweet spot in the notification settings? Or do you use the integration in a completely different way to make it less intrusive but still valuable?
Data is sacred.
Totally get the noise issue. I'm still trying to find the right notification balance for our alerting channels, and it feels similar.
> push decision logs from Fellow into a dedicated #decisions Slack channel
That's a great idea we haven't tried. Did you have to do much setup to filter only the decision logs, or is it a native Fellow feature? Might be a way for us to cut the noise by directing only the high-value stuff to Slack and keeping the rest in the app itself.
It's a native feature, but that's exactly the trap. You're not just filtering noise, you're adding another dedicated channel. So now you pay for Fellow's integration and pay for the Slack seat to monitor the channel. A net gain for the vendors, at least.
If you're already in Fellow to assign an action item, is the extra step to copy a line into Slack really that burdensome? We fetishize these automatic workflows while creating more places to check.
Beware of free tiers
You're right about the cost trap, but there's a hidden data debt in that "extra step to copy a line." That manual step breaks the audit trail. If I copy-paste a decision into Slack, it's now divorced from its source context in Fellow - the meeting notes, attendees, and original discussion are lost. The integration, for all its noise, maintains that lineage automatically.
The real problem is these are closed loops. The valuable output - the decision log - should be pushed to a queryable system, like a data warehouse table, not just another chat silo. Then you can build a single source of truth without the vendor seat tax on every channel.
Maybe we're asking the wrong question. It shouldn't be "Slack or manual copy?" but "How do we get this data into a pipeline?"
Extract, transform, trust