"I'll send you the case study" is said on the call and forgotten by the afternoon. The buyer remembers. This tutorial shows how Fivo captures those promises, how to make sure they are owned and dated, and how to check later whether they were kept.
What you need
- A meeting with its report ready in Fivo. See Meeting reports.
- Optional: Trello, Jira or another task tool connected, to share tasks and sync their status.
- Optional: an AI assistant connected over MCP.
1. Open the report
When the call ends, the report of the meeting is in Fivo: summary, chapters, tasks and participants. Open it from Home. The tasks section lists the action items Fivo detected, each assigned to the speaker who took it when possible.
2. Review the detected tasks
Read each task and fix what the model got wrong: an owner that should be someone else, a missing due date that was said out loud, a duplicate. Delete tasks that are not real work. This takes two minutes and it is what makes the rest reliable.
Tasks also appear on your Home screen across meetings, so you can do this from there for several calls at once.
3. See the commitments the Brain recorded
Tasks are the work. Commitments are the promises. Once the report is processed into the graph, ask in the AI Brain view or in your assistant: "what did we commit to on today's call with Acme?"
The answer lists each promise with its owner, counterpart, date when one was mentioned, and the report as source. You will usually see commitments that are not tasks, such as "we'll check with legal and come back to you", and tasks that are not commitments, such as internal preparation. Both are useful.
See Tasks and commitments for the distinction.
4. Share tasks to your task tool
From the report, share the tasks that belong in your team's workflow to Trello, Jira or another connected tool. Fivo creates the card or issue and keeps the link. From now on, when the card moves at the origin, its status syncs back to the Fivo task and the graph records the change with its time.
5. Share the summary
If you want participants to see the same list, Fivo can email a summary after each processed meeting to only you, to everyone on the invite, or to nobody; the setting is described in Meeting reports. Sending the summary to the client is a quiet way to confirm what was agreed.
6. Check progress during the week
Ask "what is overdue?" or "what did I commit to this week?" from Fivo or your assistant. Commitments default to you, so no further detail is needed. For a client: "what did we promise Acme that has not been delivered?"
Each open item links to its source. If something is shown open but was done, mark the task done and the commitment it matches resolves as fulfilled.
7. Watch the other direction
Commitments go both ways. "What did Acme promise us?" lists what the client owes: the signed order form, the data export, the name of the security contact. Before chasing, you have the date and the call where they said it.
8. Let the consultant catch what you miss
On paid plans Fivo scans the graph daily for dropped promises and decisions with no owner, no ticket and no next step. These show up on their own, so a promise made three calls ago does not depend on anyone remembering it.
9. Close the loop on the next call
When you prepare the next meeting with the same people, open commitments are the first section. Deliver, or explain, before they ask. See Prepare a meeting with your Brain.
What's next
- Connect code and project tools to sync task status from Jira, Linear, ClickUp and others.
- Questions your AI can answer for more ways to query commitments.
- Build a 360º brief of an account to see commitments next to everything else about a client.
- commitments
- tasks
- follow-up