Anyone else find Fellow meetings still end up with loose action items?

I've been using Fellow for several months now across two different teams, primarily drawn to its promise of structured meeting agendas and, crucially, the tracking of action items. The integration with calendar platforms and the ability to push those items directly into project management tools like Jira or Asana seemed like the perfect antidote to the chronic "wait, who was doing what?" problem that plagues post-meeting syncs.

However, after extensive observation, I've concluded that the tool itself is only a partial solution. The failure state I'm seeing isn't a software bug, but a human-process one. We meticulously build agendas in Fellow, discuss points, and assign action items with due dates during the meeting. Yet, a week later, I find myself scrolling through the meeting notes to rediscover what was agreed upon because the items have faded into the background. The intended workflow—where the assigned person receives a notification and the item lives in their "My Actions" list—seems to break down in practice.

My hypothesis is that the issue stems from two primary gaps:

1. **Notification Fatigue and Context Loss:** The assigned action item notification is just another notification in a sea of Slack pings and emails. Without an enforced process to review "My Actions" at the start of each day or week, it gets lost. Furthermore, the action item, once created, lives in a silo within Fellow. If your team's primary workflow is a Kanban board, the fact that it *can* sync to Jira is irrelevant if no one consistently executes that "push" step during the meeting.
2. **Lack of Post-Meeting Accountability Cadence:** Fellow excels at the *during-meeting* capture, but doesn't enforce a *post-meeting* follow-up ritual. There's no built-in, automated "Action Item Digest" that re-lists all open items from the last 7 days to the team, for example. The accountability loop isn't closed unless a human manually creates a follow-up agenda point for the next meeting to review past actions.

I've attempted to mitigate this by instituting a manual process. At the start of every team sync, we now have a standing agenda item called "Review Action Item Backlog." I, as the meeting lead, must manually:
* Open Fellow
* Navigate to the previous meeting's notes
* Read out each unresolved action item
* Ask for a status update

This is ironically a step *backwards* in efficiency, adding manual overhead that the tool was supposed to eliminate. It feels like we're using a powerful note-taking system but have grafted a separate, clunky accountability system onto it.

I'm curious if others in the community have hit this same wall and, more importantly, what process adaptations or integration setups you've found that genuinely solve for this. Have you successfully tied Fellow's action items into a daily stand-up bot? Are you using the API to build a custom digest? Or have you accepted that a certain level of manual follow-up is an inescapable part of team coordination?

testing all the things