Meetings
Meeting notes usually die in the tool that recorded them. Here every call arrives attached to the project it was about, with its transcript, its summary and its action items.
Fireflies records the call. The import brings across the transcript, the duration, the participants and the structured notes, and files the whole thing against a project.
Filters sort by project, by participant, and between your meetings and everyone's. An Unassigned filter catches calls that landed without a project, and Move reassigns them.
A meeting detail page holds Overview, Action Items, Detailed Notes in sections, Participants, Meeting Analytics and the full transcript.
Signals are the unusual part. Each meeting gets a risk read, admin only, with a verdict and detected flags. One real flag is No client present, which is exactly the thing nobody notices until a project is three calls deep.
Every signal is stamped with the prompt version and the model that produced it. An admin can open the prompt, edit it, publish a new version, and re-run the analysis over recent meetings.
That stamp matters more than it looks. Two signals written three months apart may disagree because the prompt changed, and the version on each one says so rather than leaving a manager to wonder.
The live instance has 49 meetings imported. The point of the prompt library is that a company can change how its own calls get read without waiting for a release.
What it does
- Filed against a project
- Meetings arrive linked to the project. Unassigned ones are filterable and can be moved.
- Signals with a verdict
- An admin-only risk read per meeting, with flags such as No client present.
- Versioned, editable prompts
- The prompt behind the analysis is editable by an admin, carries a version, and can be re-run over recent meetings.
- Import by ID and resync
- A missed meeting can be pulled in by its ID, and a whole filtered list can be resynced.
What it needs before it works
- Fireflies connected, with an API key and a webhook secret. Fireflies records the call; the import files it against the project.
- The OpenAI integration has to be on for signals. The transcript imports either way; the risk read is the part that needs a model.
- Projects have to exist so meetings have somewhere to land. Anything unmatched sits in Unassigned until someone moves it.
- Signals are gated by permission and are admin only by design.
- Somebody should watch the Unassigned filter for the first month. Meetings that land without a project are the ones that go missing, and a weekly sweep fixes it.
Questions people ask
How do meetings get into PeopleMuster?
Through the Fireflies integration. Fireflies records and transcribes the call, and the import files it against the right project with the signals layer on top.
Who can see a meeting's risk signals?
Admins. The product labels signals admin only, and the prompt behind them is documented as never posted to Slack.
Can the risk analysis be changed without a release?
Yes. The prompt is edited in the product, saved as a new version, and re-run over recent meetings. Older signals keep the version that produced them.