Skip to content
Docs

Memory

Dija maintains one shared, versioned memory for your team on Memory: concise notes that guide conversations and jobs, paired with full-text search across notes, past jobs, and messages.

What lives on Memory

Memory organizes active notes into five tabs, alongside Proposed and Archived:

  • Company brain: Core facts read in every conversation and job (what your company sells, who buys it, and why they choose you), structured as one note per topic. Click Ask Dija to draft it to generate a draft from your website. Ask "Learn how we sound" and Dija writes a How we sound note from the emails, calls, and posts your team actually sends, which outranks what the website suggests. This tab also holds How Dija speaks, which sets how Dija talks internally with your team (name, tone, language, and brevity, separate from how outreach to customers sounds).
  • Subjects: Working notes about internal projects, campaigns, launch plans, or initiatives, and one note per competitor kept by Dija marketing method. Dija writes these as it works and loads them automatically whenever a later job touches the same subject.
  • People: Each teammate's working preferences, read in every job run for that person, including How I write, which Dija can learn from your own sent emails when you ask ("Learn how I write"). It is proposed to you, and only you can approve it.
  • Tools: How your team uses each connected company tool (pipeline stages, custom fields, ownership conventions). Dija writes one automatically when a company tool first connects.
  • Skills: Your company's custom instructions layered over Dija's built-in skills, or custom skills written in chat. See Skills and methods.

What belongs in your tools instead

Your connected tools stay the source of truth, and Memory holds only what none of them holds. Facts about external companies and contacts (prospects, customers, or partners) belong on their records in your CRM, where your whole revenue stack can see them, so Dija logs them there rather than in Memory. When a note and a record in a connected tool disagree, Dija goes by the record. Competitors are the exception: what Dija learns about them is your own positioning, so it stays in Memory. If you have not connected a CRM yet, those findings remain in each job's result log, where search still finds them.

Permissions by note type

Note typeWho can edit directlyWho can approve proposals
Company brain, ToolsAnyone on the teamManager or owner
SubjectsAnyone on the teamAnyone on the team
People (preferences)That person, their manager chain, or ownerThat person
SkillsManager or owner (members submit proposals)Manager or owner
How Dija speaksOwner onlyOwner only

Saved immediately vs. proposed for review

  • Direct instructions in chat: When you tell Dija to remember or update something, Dija saves the note right away if your role can edit it directly, or creates a proposal if not. (On phone calls or through external assistants like Claude or ChatGPT, Skills updates are always proposed and How Dija speaks cannot be changed; see Approvals and rules.)
  • Notes learned during a job: Dija saves Subjects, Company brain, and Tools notes immediately. When it changes a Company brain or Tools note, it tells the teammate who leads that work (the person who asked, if they are a manager or the owner, otherwise the first manager or owner above them), once for each note in a job, with what it saw and a link to the note, where Versions lets them restore the earlier text. People and Skills notes learned mid-job are submitted as proposals with supporting evidence, routed to the person whose preferences they are or to the first eligible approver in the requester's reporting chain up to the owner. A job never changes How Dija speaks.
  • Notes from private jobs: Any note learned during a private job is proposed privately to you first. See Private and shared work.

For a proposal, Dija notifies the approver once with a link, and the item waits on Approvals and Memory > Proposed. Approvers can click Approve, click Correct then Approve my version, or click Reject. Memory proposals do not send reminders or escalate, and a newer proposal for the same note replaces an older pending one.

Version history and archiving

Every edit creates a new version. Open Versions on any note to read past revisions, and click Restore to make an earlier version current again.

Click Archive (with an optional reason) to take a note out of active use while keeping its version history. On the Archived tab, Bring back restores it unless an active note now shares the same title. On its own, Dija archives Subjects, Company brain, and Tools notes when merging duplicates or retiring clearly outdated context, and tells you about a brain or tool note the same way as a change. People and Skills notes are yours to archive; when one should go, Dija says so in the job's result.

Monday memory tidy

Every Monday at 06:00 in the workspace owner's timezone (or whenever you ask Dija to tidy memory in chat), Dija runs a maintenance job for the owner that:

  1. Proposes moving any external company or contact facts onto CRM records (subject to normal tool approvals).
  2. Merges overlapping Subjects, Company brain, and Tools notes (for example, two notes on how your team uses one CRM) and archives clearly outdated ones, such as the old tool note of a tool that was connected again.
  3. Saves shorter texts of overgrown Company brain and Tools notes and proposes shorter texts of People and Skills notes, without inventing facts, dropping still-relevant details, or changing How Dija speaks.
  4. Lists brain or tool notes that contradict each other in its result, for a person to settle.