Company Brain

Navigate

Open the upload workspace

For support and operations teams

Turn tickets, macros, notes, and docs into reviewed SOPs and decision rules.

Bring one team's tickets, macros, notes, transcripts, and docs. Company Brain turns them into source-backed drafts so a named process owner can decide what the team should follow.

Open the upload workspaceSee a reviewed example

Available now: upload files, ZIP exports, or paste text.

Read-only Zendesk connection is not yet available to customer workspaces.

What gets approved

Your team's source materialSOURCE

Tickets, macros, docs, transcripts, notes, and exports from one team or function.

Human review

Reviewer-approved guidance

Each approved item keeps its source, owner, approval state, and reviewer details.

Product demonstration

See a source-backed rule go from draft to approved.

The synthetic ticket, saved macro, and billing note disagree about refund handling. See how the draft keeps those sources visible until Maya resolves the conflict and approves one rule.

Synthetic product demonstration

Refund escalation rule

One support team's records

  1. 01

    Source material

    Tickets, macros, and maintained notes

    Zendesk connection

    Not yet available

    Read-only Zendesk connection is not yet available to customer workspaces.

    Uploads and exports

    Available

    Upload files, ZIP exports, or paste text from one team.

  2. 02

    Drafts for review

    Rules, gaps, and conflicts surface

    Draft rule

    Custom terms require Billing Ops review before a promise.

    Knowledge gap

    No named owner for partial-credit approval.

    Conflict

    The saved macro says 24 hours; the billing note says 3 days.

  3. 03

    Human review

    Maya Chen · Support Operations

    Reviews every draft against its source before anything can be approved.

    Needs edit · assign the partial-credit owner

    Approved · standard refund intake rule

    Rejected · outdated 24-hour promise

  4. 04

    Approved rule

    Standard refund intake rule

    Verify purchase window, plan tier, refund reason, and custom terms. Route exceptions to Billing Ops before promising an outcome.

    Owner
    Support Operations
    Sources
    Ticket 1842 · macro v7 · billing note
    State
    Approved · current · exportable

How it works

Bring the source material. Review every draft. Share only what the process owner approves.

  1. 01

    Bring source material

    Start with one team's records—not a company-wide migration.

    Bring the tickets, macros, notes, transcripts, and maintained docs that explain one team or function. Company Brain keeps every draft tied to the records it came from.

    One team or function · one clear set of source material

    See how to bound a helpdesk connection
  2. 02

    Review every draft

    AI drafts. A named process owner decides.

    Company Brain drafts source-backed SOPs, rules, gaps, conflicts, macros, and FAQ entries. The process owner edits, approves, rejects, or marks each item as Needs edit.

    Nothing is approved without the process owner's decision

    See why every draft needs review
  3. 03

    Share approved work

    Export only the SOPs, rules, FAQs, and macros your process owner approves.

    Your team gets the approved SOPs, decision rules, FAQs, and macros to use. Rejected items stay out, and approved items stay linked to their source references.

    Approved item · source · owner · review state

    See what your AI tools should receive

What your reviewer can verify

Inspect the claim, source, owner, and approval state.

This synthetic example shows the minimum context a reviewer needs before a rule can be trusted. The draft keeps identified gaps and conflicts visible for the reviewer to resolve before approval.

See a reviewed operational knowledge pack

Realistic synthetic output

Partial-credit decision rule

Approved

If an account has custom terms, support gathers the contract context and routes the request to Billing Ops before promising timing or amount. Standard in-window requests follow the approved refund intake SOP.

Reviewer
Maya Chen · Support Operations
Provenance
Ticket 1842 · macro v7 · billing note
Resolved conflict
Replaced the unsupported 24-hour promise
Next review
When refund terms or source records change

Provenance

Every draft keeps the source context your reviewer needs.

Review state

Draft, Needs edit, Approved, and Rejected remain distinct.

Boundaries

One team or function, one set of records, one named reviewer.

Sharing

Only the SOPs, rules, FAQs, and macros the process owner approves are ready to share.

Data and securitySupported files, limits, and trial FAQHow to choose one team's source material

Start with one team

Give your reviewer source-backed drafts to approve—not more documents to search.

Bring files from one team or function and name the process owner who will review the drafts. Working with ordinary confidential operational files? Review how files are handled, retained, and deleted before you upload. Do not include secrets, credentials, payment data, regulated health, legal, or financial data, highly confidential strategy, private employee records such as HR, performance, disciplinary, payroll, medical, or immigration records, special-compliance material, or anything your company cannot share.

Open the upload workspaceGet scoping help