Notes are where a lot of important client context lives, but they are also one of the easiest places for information to become fragmented.
In practice, notes can end up:
spread across meetings, emails, and personal documents
inconsistent in format
hard to find later when you actually need them
When notes are not structured or connected to the right client or household, it becomes harder to:
prepare for future meetings
understand past decisions
collaborate across the team
build a reliable history of the relationship
Notes in Vega
In Vega, notes are designed to stay connected to the broader client context.
This means:
notes can be linked to contacts and/or households
notes appear in the Activity section alongside meetings, emails, and tasks
notes become part of Vega’s knowledge when generating future outputs (meeting prep, drafts, chat responses)
The goal is not just to “store” notes, but to make them usable.
How to create notes
There are several ways to create notes in Vega depending on where the information is coming from.
Chat threads & Push-to-Talk (PTT)
You can create notes directly from a Vega chat thread.
For example, you can type or dictate:
“Create a note for the Smith household that they are traveling to Spain next week.”
Vega will generate a structured note that you can review and save.
This is often the fastest way to create notes because you can describe them naturally instead of filling fields manually.
Manually
You can create a note manually by clicking the (+) button at the top right of the Vega web platform and selecting New note.
This is useful when:
you want to capture something quickly
the note is not tied to a meeting or email
you already know the structure you want to use
Vega AI Email Assistant
Notes can also be created from your inbox.
For example, after reading an email, you can ask Vega to:
summarize the email into a note
create a note linked to a client or household
This is useful when important information comes through email and you want to capture it in a structured way right away.
Post-meeting summary notes
This is where Vega behaves differently from tasks, and it’s important to understand the distinction.
After a meeting, Vega generates post-meeting summary notes automatically.
Unlike tasks:
Vega does NOT suggest creating a separate “Note” object from these summary notes
you do NOT review them as a standalone note suggestion to sync
Instead, the post-meeting summary notes are saved as part of the meeting itself.
Any edits you make to these notes, whether using the AI Rewrite feature, editing them manually, or re-running the meeting to generate a new version, are automatically saved as part of that meeting’s knowledge.
Each meeting becomes a structured record that includes:
the post-meeting summary notes
the follow-up email draft
the transcript
As long as the correct contact or household is linked to the meeting:
the content of the meeting (including the notes) becomes part of Vega’s knowledge for that client and household
This means you can:
search for it later
reference it in future meetings
ask Vega questions about it in the chat
A useful way to think about it
Post-meeting summary notes = part of the meeting record (automatically stored, no separate note needed)
Manual or AI-created notes = standalone records you create when needed outside of a meeting
Both are important, but they serve slightly different purposes.
Post-meeting notes capture the full context of a conversation. Standalone notes allow you to capture additional information that does not come directly from a meeting.