Org Context for AI Agents

Created by Manuk Shirinyan, Modified on Thu, 8 Oct at 12:13 AM by Aye Myat

Note: Feature(s) Pending Rollout

Features and functionality described on this page are part of our October 2026 release, which is rolling out to eligible customers October 8-October 27, 2026. See our Release Notes here to learn more.

Objective

Learn how to set up and manage Org context so AI Agents understand your organization and tailor their responses to it.

Applies To

  • Outreach Admins

Before You Begin

  • Org context is shared across your organization. Any active content you add shapes AI Agent responses for everyone.

Overview

Org context gives AI Agents always-on knowledge of who your organization is: what you sell, who you compete with, and how you sell. Admins curate this context on a dedicated page, and AI Agents use it to keep their responses relevant to your business.

Without this context, AI responses can be generic and miss the specifics that matter to sellers. With Org context, users don't have to re-explain company basics in every conversation.

Org context is organized into blocks. Each block has a title, a description, and a free-form body (except for Company Overview block, which is split into sections). Three blocks are included by default:

  • Company overview
  • Competitors
  • Products

You can edit these blocks, delete them, or add your own.

A few things worth knowing about how this works:

  • Blocks can be active or inactive. AI Agents read active blocks at every turn of a conversation. Inactive blocks are ignored until you activate them.
  • You can fill in blocks manually or have Outreach populate them from a web search. You can preview, accept, or reject suggested content, and the sources used are shown in a References section.
  • Deleted blocks can't be recovered. If you want to stop using a block temporarily, set it to inactive instead.

Procedure

Set Up Org Context

  1. Log in to Outreach as an Admin.
  2. Go to AI toolkit > Org context.
  3. Start with the default blocks (Company overview, Competitors, Products), or add a new block.
  4. Fill in the block manually, or select Populate from web.
  5. If you used Populate from web, review the suggested content and its sources, then accept or reject it.
  6. Set each block to active or inactive as needed.

Repopulate Org Context

  1. Log in to Outreach as an Admin.
  2. Go to AI toolkit > Org context.
  3. Click the ... (ellipsis) menu.
  4. Select Repopulate all content.
  5. Review the suggested content, then accept or reject it.

Note: Don't include personally identifiable information (PII) or protected health information (PHI) in Org context blocks. Active content is used across your organization's conversations.

Additional Information

FAQ

What does Org context do?
It gives AI Agents ongoing knowledge of your company, products, competitors, and sales motion, so their responses reflect your organization without users having to explain it each time.

Do inactive blocks affect AI Agent responses?
No. Only active blocks are read by AI Agents. Inactive blocks are kept on the page but not used until you activate them.

Can I recover a deleted block?
No. Deleted blocks can't be recovered. To pause a block without losing its content, set it to inactive.

Where does populated content come from?
Outreach searches the web for information about your organization. The sources are shown in the References section so you can verify content before accepting it.

Can I populate blocks from internal documents or file uploads?
Not at this time. Blocks can be populated from the web or filled in manually.

Can I roll back to a previous version of my Org context?
Not at this time.

How is Org context different from Knowledge and which one to use?

Org context is a short, curated summary of your organization that admins maintain. AI Agents read all active Org context blocks at every turn of a conversation, so this information is always applied.

Knowledge is a library of uploaded company documents. AI Agents search it and pull in only the passages that seem relevant to a given question, so any one document may or may not be used in a response.

Use Org context for core facts every response should reflect, such as what you sell, who you compete with, and how you sell. Use Knowledge for detailed reference material, such as product documentation, playbooks, or case studies.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article