Book a demo Sign up

Context Studio: every answer starts with the right context.

Context Studio is where you define, test and govern what Kroolo AI knows about your business: definitions, policies, playbooks and sources. Versioned, permission-aware and shared by every agent.

Context StudioVersion 14Live
GuidesSourcesDefinitionsEvals
business-context.mdCompany, products, glossaryLive
metric-definitions.mdARR, churn, net revenue retentionLive
escalation-playbook.mdSupport routing and SLA rulesDraft
Salesforce: AccountsSynced 4 minutes agoSource
Context health94%
3 suggested fixes from this week's questions
Unified context

Define it once. Every agent uses it.

Most AI mistakes are context mistakes: a metric defined two ways, a policy nobody told the model about. Fix the context once and every answer, agent and workflow improves with it.

Start from what you have
Bring in documents, wikis, tickets, metric definitions and policies as they are. No long modelling project before you see results.
NotionConfluenceSharePointGoogle DriveGitHubSalesforce
Written in plain language
Subject experts add guides and definitions in plain text. Data and platform teams can sync the same files from Git. Every change is versioned.
# metric-definitions.md
ARR = recurring subscription
revenue x 12, excluding one-off fees.
# owner: Finance
Reaches every surface
One source of truth for Chat, Search, Agents and workflows, and for your own tools through MCP and API.
ChatSearchAgentsWorkflowsMCP and API
Governed by design

Context as code. Governance built in.

What your AI believes about the business should be reviewed like anything else that matters.

Versioned and reviewable
Every edit is a change request with a diff, an owner and a history you can roll back.
Approved by the right people
Route changes to the team that owns the definition before they reach any agent.
Permission-aware by default
Answers only draw on context and sources the person asking can already open.
Auditable
See which context shaped each answer, and when it last changed.
Change requestIn review
Update the ARR definition
metric-definitions.md · proposed by the Review agent
- ARR = MRR x 12, including one-off fees
+ ARR = recurring subscription revenue x 12,
+ excluding one-off and usage fees
Eval run: 42 questions, 41 unchanged, 1 improved
FLFinance leadOwner of revenue metricsApproved
DLData leadPlatform reviewerPending
Approve and publishRequest changes
Observable everywhere

See what your AI is asked, and where it struggles.

Every question asked in Chat, Search, agents and connected tools shows up in one place, with the context that shaped the answer.

Context observabilityLast 30 days · all roles · all sources
461
Conversations
55
Unique users
12
Warnings
Conversation volume
Top topics
Revenue38%
Churn24%
Pipeline19%
Hiring11%
Other8%
QuestionTopicWarningSourceRole
What was net revenue retention last quarter?RevenueConflicting definitionSlackSales
Show churn by segment for APACChurnMissing contextChatFinance
Which deals are likely to slip this month?PipelineNo warningSearchSales
How many open roles are past 60 days?HiringNo warningMCPPeople
Trends surface on their own
Rising and new topics are grouped for you, so you see what the company is starting to ask before it becomes a problem.
Warnings point to the fix
Confusion, missing context and doubtful answers are flagged with the source involved, and a suggested edit is ready to review.
Improves with use

Gets sharper with every answer.

Context is not a project you finish. Studio closes the loop between what people ask and what your AI knows.

Step 1
A gap is found
The same question gets warnings nine times in a week: nobody agreed what "ARR" means.
Which deals will slip this quarter?
Kroolo AI
4 deals ($84k) have no activity in 14 days.
Step 2
A fix is suggested
The Review agent drafts the missing definition and links the questions that exposed it.
What changed in my pipeline today?
Kroolo AI
2 deals moved to Proposal; 1 slipped a week.
Step 3
It is tested first
Changes run against your eval questions. Anything that makes an answer worse is caught before it ships.
What changed in my pipeline today?
Kroolo AI
2 deals moved to Proposal; 1 slipped a week.
Step 4
It goes live
Approved, versioned and published. Every agent uses the new definition from the next question.
What changed in my pipeline today?
Kroolo AI
2 deals moved to Proposal; 1 slipped a week.
Accuracy on your eval set
Before and after the ARR change, measured on the same 42 questions.
Before78%
After94%
Bring your own context

Works with the stack you already run.

Pull knowledge from your tools, write it in Studio, or sync it from Git. Context stays portable, so you are never locked in.

Connect your tools
Documents, tickets, chat and data platforms through 50+ native connectors, or any MCP server.
Manage it in Git
Keep guides and definitions in a repository, review changes in pull requests and run evals before shipping.
Bring your semantic models
Sync metric definitions from the models you already maintain and keep them versioned at the source.
Browse all connectors
Notion
Confluence
SharePoint
Google Drive
GitHub
Jira
Slack
Salesforce
Snowflake
Databricks
Power BI
Tableau

FAQs on Context Studio

What can be context?
Guides and definitions written in Studio, documents and wikis, tickets and chat history from connected tools, metric and semantic models, and the work your teams publish. You can start with a single file and add more over time.
Do we need a semantic model first?
No. Semantic models suit metrics that must be calculated the same way everywhere, and Studio can sync them if you have them. For everything else, a plain-language guide or a trusted document is enough to start.
Can we see which context shaped an answer?
Yes. Each answer records the guides, sources and definitions it used, so reviewers can audit the reasoning and see when that context last changed.
How does it respect permissions?
Context is filtered at retrieval by the permissions of the person asking. An answer never draws on a source that person cannot already open.
How are changes tested before they ship?
Every change can run against a set of eval questions you choose. You see which answers improve, which stay the same and which get worse, and only approved changes are published.
How much maintenance does it need?
Less than a modelling project. The Review agent flags gaps and drafts fixes from real questions, and work your teams publish adds context as a by-product.
Is our data used to train models?
No. Your content is not used to train models, and each tenant is isolated.

Give every answer the right context.

Bring a real question your AI gets wrong today. We will show where the context is missing and how Studio fixes it.