Business Context lets you give Optimize's AI agent background about your organization: your goals, tools, and teams, so its chat answers are relevant and specific from the very first question, instead of generic.
What is Business Context?
Business Context is org- or team-level background information that you add once, which Optimize's agent then automatically applies to every future chat conversation. Instead of re-explaining your company, tools, or team structure every time you open a new chat, you set the context once and the agent remembers it going forward.
Where do I add it?
Business Context lives in Settings → Business Context. It's visible to Team Optimizers and above (Team Optimizer, Org Optimizer/System Admin roles) — a Participant-only user won't see this tab.
- Org Optimizers / System Admins can add or edit Business Context for the whole organization, and for any team.
- Team Optimizers can add or edit context for the teams they have access to.
You can also update Business Context conversationally, right in agent chat — just tell the agent what's changed (e.g., "our team just started using Salesforce instead of HubSpot") and it will propose an update and apply it, no trip to Settings required.
Org-level vs. team-level context
Context can be set at two levels, and they layer rather than override:
- Organization-level context applies company-wide — things like company size, tool stack, integration layer, and overall goals.
- Team-level context applies on top of org-level context for a specific team — things like team roster/headcount, that team's specific workflows, working style, or constraints.
Setting team-level context does not replace or override org-level context — the agent uses both together.
What should I include?
- Org structure and company size
- Tool stack and integration layer (what systems you use, how they connect)
- Team sizes/rosters by function
- Priorities and KPIs (e.g., "we care about hours saved and reducing headcount growth")
- Known constraints (compliance requirements, integration limitations)
- Upstream/downstream handoffs between teams
- Existing process documentation
A good rule of thumb: if you find yourself re-explaining the same background information in multiple chat sessions, that's a sign it belongs in Business Context instead.
When should I add or update it?
- When you first set up Optimize, especially if you're a multi-team org where context varies by team.
- Any time your org changes — new tools, reorganized teams, new priorities — update it conversationally in chat or in Settings so the agent's answers don't go stale.
- If agent answers feel too generic or don't reflect how your business actually works, adding or refining Business Context is the first thing to try.
Here's a Scribe Page with best practices and Templates:
Good to know
- It's forward-looking only. Business Context applies to new conversations after it's added or updated — it does not retroactively change past conversations or previously generated insights.
- It affects agent chat, not the mined-workflow analysis. Business Context you add in Settings (or via chat) shapes what the agent says in conversation. It does not change what shows up in the Top Issues or mined workflows tabs — that analysis is driven by a separate, backend pipeline configuration that your Scribe team manages directly with you.
FAQ
Who can set Business Context? Team Optimizers and above (Team Optimizer, Org Optimizer, System Admin) can add or update it — either in Settings or conversationally in agent chat.
Does team-level context override company-wide context? No, team-level context layers on top of org-level context; it doesn't replace it.
Does it apply to past conversations? No, only to new conversations started after the context was added or updated.
Does Business Context change my Top Issues or mined workflow recommendations? No, that's a separate, backend-configured layer. What you add here only affects agent chat answers. If you want your recommendations tuned as well, talk to your Scribe team.