Resources
FAQ
These answers explain how to start with source material from one team, who reviews the drafts, what Company Brain stores, and what the current trial supports.
You should know what the current product trial supports and what it does not promise.
Is Company Brain a chatbot?
No. The trial is not a chat-with-your-docs experience. It turns one team's source material into structured operational drafts for a named owner to review; it is not a generic chatbot, enterprise search tool, wiki, or full company knowledge graph.
Do we need live integrations?
No. Today, customer trials start with uploads, ZIP exports, supported folder uploads, or pasted text. The Zendesk connection is not currently available to customer workspaces.
Do we need a credit card?
No credit card is required to start a normal trial. If a later extraction needs more prepaid credit than the workspace has, the product may offer an optional top-up, reduced scope, or support; normal in-allowance trial use remains free.
How long does extraction take?
A full set of team files can take 10 minutes or more. Smaller focused sets may finish sooner; larger sets may need scoping help.
How many source files should we bring?
Bring enough relevant files, tickets, notes, transcripts, exports, or pasted excerpts to show repeated patterns without turning the trial into broad cleanup. Keep the first source set within one team, queue, operating area, or reviewer owner.
Can we upload PDFs, DOCX files, or ZIP exports?
Text-layer PDFs with selectable text, readable DOCX files, and supported text-like entries inside ZIP uploads are parsed in the browser. Scanned PDFs are not OCRed, protected or image-only DOCX files cannot produce extracted text, and unsupported, nested, unsafe, too-large, corrupt, encrypted, or password-protected ZIP content is skipped or failed clearly.
Who approves the output?
One designated reviewer or process owner approves, edits, rejects, or marks items as needs edit. Draft output is not approved policy until that review happens.
Does Company Brain publish directly into our tools?
No. The current product exports reviewed output for your team to move into the right help center, playbook, macro system, or internal docs workflow.
Do we need to redact our files?
No. Ordinary confidential operational files can be used when they come from one team or operating area. Redacted or sanitized examples are still fine, but manual cleanup is not required for normal business documents. Restricted material stays out of scope. Review data handling and security.
Why does the trial stay within one bounded team or function?
A bounded source set gives one reviewer a coherent pack to inspect instead of turning the trial into broad company cleanup. Start with one team, function, queue, or operating area and the source material that belongs to it.
What happens after we upload?
Company Brain extracts draft SOPs, decision rules, gaps, conflicts, FAQs, and support macros. One reviewer then edits, approves, rejects, or marks each item as needs edit before exporting the useful pack. See how the trial works.
What does Company Brain store?
In the current upload flow, your browser sends readable text for processing but does not send the original file bytes. The hosted trial retains filenames and parse metadata, short text previews, run hashes and summaries, and source-derived content in evidence quotes, generated packs, review edits, exports, and debrief answers. Full extracted source text is not stored as a separate retained field after the request finishes. Review data handling and security.
How are retention and deletion handled?
Company Brain does not yet offer self-service retention settings or a published automatic deletion schedule. Support can provide a scoped export or tombstone an organization's active datastore: sessions are removed, identities and customer content are removed or anonymized, and minimal run and trial-usage audit records remain. Recovery backups may contain earlier copies, so this is not an immediate deletion guarantee for every backup. Review the current retention and deletion boundaries.
Can we start ourselves, or do we need an invitation?
A normal low-volume trial can start through the public upload-first trial without an invitation. Use guided scoping when the team boundary, reviewer, or source set needs help before the run. Controlled invite-created workspaces remain available for guided cases.