Meetings

Meetings at /meetings holds AI-transcribed records of scheduled contact: what was discussed, what was decided, and what follows. The calendar view of when things happen lives at Scheduling; this surface is what happened.

• The header states the contract: “Review AI-transcribed meetings, summaries, and key insights.” Totals headline it: meeting count, average duration, average sentiment. Search, sort, views, columns, filters, owner, company, and time range narrow the list.
• The table lists meeting, date, transcript link, and status per row, each linked to its transcript. Status reads processed once transcription lands.
• The transcript link is the record; the summary is the shortcut. When a follow-up is disputed, open the Fireflies transcript before re-litigating the summary.

• Every meeting ends with named follow-ups or it did not end. Decisions attach to the rows they concern — deals, deliverables, project records — not to the meeting alone. Follow-ups become assigned work at Tasks.
• Meetings are adjacent to CRM activity, not part of it. Notes, logged calls, and tracked emails live on the Activities hub; synced calendar entries live at Events.
• Repeatable meeting shapes belong in Templates. If the same agenda gets rebuilt every week, the template should exist.

What next

• Activities: the shared activity model — adjacent, not overlapping.
• Events: calendar-synced entries per record.
• Scheduling: the calendar view behind these records.
• Tasks: where meeting follow-ups become assigned work.
• Templates: repeatable agendas and meeting shapes.
• Team: the member side of the attendee list.