Brain document categories

When you upload a document to Brain, you pick a category. The category controls which agent contexts the document gets injected into, so getting it right matters.

Categories

sales_sop — Sales SOP

Your discovery framework, qualification rubric, pricing playbook, close playbook, objection-handling library, deal-review checklist.

Agents that pull from this category: - Outreach drafts (Origin agent) - Account briefs (Account Prospecting agent) - Customer Success agent (every run)

Good examples: "Discovery Call Framework v3.pdf", "MEDDIC qualification scorecard.docx", "Tier-1 pricing approval policy.md".

voice_tone — Voice & tone

Exemplars of how your brand writes. Cold emails, follow-ups, proposals, internal Slack tone, anything that demonstrates your house style.

Agents that pull from this category: - Outreach drafts (Origin agent) - Customer Success agent - TOV Database scoring

Good examples: "Sample cold email — Outreach v4.pdf", "Brand voice guidelines (longform).docx", "Three winning sequences from Q4.md".

deliverable — Deliverable templates

Documents your team produces for customers — proposals, project plans, summary one-pagers, post-mortem reports. The Customer Success agent uses these as structural and stylistic templates when generating client-facing artifacts.

Agents that pull from this category: - Customer Success agent (when generating deliverables)

Good examples: "Proposal template — Enterprise.docx", "Quarterly Review one-pager.md", "Onboarding plan template.pdf".

brand_guideline — Brand guidelines

Visual and verbal brand standards. Color usage, typography rules, logo usage, taglines, do-not-say list. Less referenced today but pivotal for v1.1's branded deliverable rendering.

Agents that pull from this category: - Customer Success agent (in v1.1 when rendering branded outputs)

Good examples: "Brand book — 2026.pdf", "Logo usage rules.docx".

procedure — Procedures

Internal procedures that aren't strictly sales: onboarding checklists, escalation paths, account-handoff playbooks, post-deal celebration rituals. Anything operational.

Agents that pull from this category: - Customer Success agent (for handoff and lifecycle context) - Account briefs (when relevant)

Good examples: "Account handoff procedure.md", "Customer escalation tree.pdf".

other — Other

Catch-all when nothing else fits. Not preferentially injected into any agent. Usable in direct Brain chat.

How to choose

If you're unsure between two categories, pick the one that names the agent you most want this content to influence: - "I want every outreach to sound like this" → voice_tone. - "I want every Customer Success run to follow this" → sales_sop or procedure. - "I want our proposals to look like this" → deliverable.

Better to file something well than to file something twice. You can recategorize later (Replace document, change category in the same flow).

Things to avoid

• Don't upload personal CRM exports. Brain is for org-level policy/style, not the long tail of one rep's notes. Keep those on the prospect records themselves.
• Don't upload customer PII as exemplars. Voice/tone documents should be redacted before upload — Brain content is org-wide and seen by every team member.
• Don't upload outdated docs without archiving the old. Multiple "current" SOPs is the #1 way to confuse the agents. Use the version system, or archive the old before uploading the new.