An account review, a handover or a renewal all need the same thing: everything the company knows about one client, in one place, with sources. Fivo builds that from what already happened. This tutorial shows how to get the most complete brief and how to use it with your AI assistant.
What you need
- Reports of your calls with the account in Fivo, including past calls brought in from other tools. See Meeting reports.
- Your email connected (personal) and, ideally, your CRM connected with organization scope by the owner. See Connect CRM and support tools.
- Optional: your support tool and project tool, so requests and deliverables are in the graph too.
- Optional: Claude or ChatGPT connected over MCP.
1. Make sure the account exists as one entity
Search the Brain for the company name. You should see one company entity with its people, facts and sources. If you see two (one from calls, one from the CRM, for example), the graph has not merged them yet; usually a few more interactions that mention both resolve it. If an external contact appears under two names, the same applies.
2. Ask for the brief
In the AI Brain view, or from your assistant, ask "brief on Acme". The brief is the 360º dossier of the company:
- People: who decides, who influences, who went quiet, and your colleagues who worked with them.
- Decisions taken with or about the account, with dates.
- Commitments in both directions, open and fulfilled.
- Timeline: calls, emails, tickets, messages and CRM changes in order.
- Signals: competitor mentions, budget or procurement talk, long silences, a new main contact.
Every item carries its source. Nothing is typed by a human; it comes from what happened.
3. Fill the gaps
Read the brief and notice what is missing. Common causes and fixes:
- No email facts: email is personal. If a colleague handled the account, their correspondence lives in their personal graph and will not appear in yours. Ask them to check, or rely on the calls and CRM, which are shared.
- No tickets: connect Intercom or Zendesk, or add the account's project in Jira or Linear.
- Thin history: import past calls, or widen the sources Fivo reads for this account.
- Facts you expected but cannot see: check the Brain status for blind spots, and remember you only see what you could open at the source. See Permissions: what your Brain can see.
4. Ask the follow-up questions
A brief answers "what do we know". The follow-ups answer "what should we do":
- "What did we promise Acme that has not been delivered?"
- "Has Acme asked for anything outside the SOW?"
- "Which of Acme's requests shipped, and which are still in the backlog?"
- "Who at Acme has not been in a call for more than two months?"
Each answer is a short list with sources. Your assistant can run them in sequence; over MCP, the account review prompt does exactly that.
5. Draft the deliverable
With the facts assembled, ask your assistant to write what you need:
- An account review for an internal meeting: health, open items, risks, next steps.
- A handover document for a new account lead: history, key people, open promises, recent decisions.
- A client update for the month: what shipped, what is open, what changed in scope.
Ask for sources on every line. The result is a document you edit rather than one you research.
6. Hand it over, not down
For a handover, the new account lead does not need the document to be complete. They need to be able to ask. Add them to the account's space so past reports are visible to them, and point them at the brief. On their first call they will know what the previous lead knew. See Spaces and members.
7. Keep it current without doing anything
The brief is not a file. The next call, email or ticket updates it. Ask again before the next review and the timeline has moved. The daily consultant also watches the account for risks, such as a renewal date that moved while the related work did not.
What's next
- Prepare a meeting with your Brain for the short version before each call.
- Track commitments after a call to keep the promises section honest.
- What the Brain knows to understand entities, facts and sources behind a brief.
- briefs
- accounts
- crm
- handover