Guides
How to prepare source files
Good source material preserves the operational pattern. Messy source material is fine. Irrelevant or restricted source material is not.
You should know what to gather, what to exclude, and how to handle unsupported file types.
Gather a tight source set
- 1
Collect artifacts from one team corpus
Pick tickets, threads, macros, call snippets, CRM notes, or docs that all belong to the same team, queue, operating area, or policy domain.
- 2
Keep the useful mess
Include contradictions, old guidance, escalation notes, and examples where the team handled the issue differently.
- 3
Remove unrelated material
Do not upload broad exports full of unrelated customers or unrelated processes just because they are easy to export.
Exclude restricted material
- Ordinary confidential operational material is OK when it is needed for the bounded team or function corpus.
- Do not upload secrets, credentials, payment data, regulated health, legal, or financial data, private employee records, highly confidential strategy, special-compliance material, or anything your company cannot share.
- Optional cleanup is fine if your team prefers it, but do not spend time manually sanitizing normal business documents just to start the trial.
When a file cannot be parsed
If a PDF has no readable text layer, if a DOCX has no extractable text, or if ZIP entries are skipped or fail, paste the important text into the source material box or provide a text-like export. Company Brain should not pretend unsupported file types were parsed.