Loading
Because the call happens in one tool and the work in another. Decisions are made, somebody types notes into a document, and the actions are remembered by whoever was paying attention.
A meeting in Loop is a call started from a project, with its agenda, attendees, notes and resulting tasks attached to that project.
The meeting carries an agenda drawn from the project, and notes taken during it can become tasks with owners before the call ends. Everything stays on the project record.
A kick-off ends with eleven actions. They are tasks with owners and dates by the time people leave the call, and they appear in personal queues that afternoon.
It will not record and transcribe by default. A recording of everything is not a record of what was decided, and the deliberate note is the more useful artefact.
Attendees come from the project team and the client contacts in Flow; resulting tasks join the plan and count against capacity.
Yes, by link, without a Loop account.
Only if you turn them on, per meeting, with attendees told.
It does not have to. Notes and actions can attach to a project either way.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.