Where the answer comes from
Vector, lexical and entity-graph search in the same query, always at the version that applied on the date asked about, with the ACL filter applied before ranking.
Explore KnowledgeStrattum Chat answers from the Company Brain
The difference is what the Chat reads before answering, and what it hands over with the answer.
Every answer names the document, the version and the record it came from, down to the paragraph. Whoever receives it can open the source and check.
The query runs with the ACLs that person already has in Salesforce, SharePoint and the core system. What they cannot see never enters the answer.
The Chat reads Memory Graph and Knowledge in the same query, so customer, contract, ticket and policy arrive resolved across systems.
The same BYOC architecture as the rest of the platform. The question, the context and the answer stay in your infrastructure.
What discount applies to Acme today?
Up to 15%, within the account manager’s authority. Above that, approval moves to the commercial director.
Every passage in the answer opens straight in its source
How much does Acme pay per month?
The contract in force is R$ 148k per month, renewed in January for 24 months.
2 sources beyond your access never entered, and do not appear even as a citation
Why did Acme open a critical ticket?
A failure in the reconciliation module since the 12 March migration. It is the third ticket from this customer about that module this quarter.
The same Acme resolved across three systems, with nobody cross-checking a spreadsheet
Can this history leave the company?
It does not. The model is called from inside your VPC and the context never crosses that boundary.
Question, context and answer stayed in your region
The question arrives in plain language. Between it and the answer, Strattum retrieves, executes and records.
Vector, lexical and entity-graph search in the same query, always at the version that applied on the date asked about, with the ACL filter applied before ranking.
Explore KnowledgeA question that needs a calculation or a query calls the governed Skill, run in an isolated microVM with the permissions of whoever asked.
Explore SkillsEvery question keeps who asked, what was read, which policy applied and what was answered, in a log that exports to your SIEM.
Explore GovernanceIn 30 minutes we map one question that today costs four systems and a spreadsheet, and show the context it would need to be answered.