Change Log

Outreach added Org Context, a set of admin curated blocks, such as company overview, competitors and products plus custom blocks, that every Outreach AI agent references before it generates an output. Admins can write blocks by hand or populate them from web sources, accept or reject the suggested content with its sources shown, and archive blocks to keep them out of agent responses. Access needs dedicated Org Context permissions, and the October release ships to customers between 8 and 27 October.

Admins now control the shared facts every Outreach agent works from, which keeps positioning consistent and gives one place to correct what agents say.

Outreach's September release adds approval previews before its Omni assistant changes Prospect, Account or Opportunity records, along with persistent user preferences and mobile survey and record actions. It also expands participant tagging in Kaia and the call and meeting data sent to ServiceNow. The rollout runs from 10 to 24 September.

The approval preview redraws the line between an AI suggestion and a CRM write, which is the control most buyers ask about first. The rollout is staged, so confirm it has reached your tenant before relying on it.

Outreach's August 2026 release introduced an AI Control Hub for granular governance of AI features and a configuration change log for Revenue Agent, alongside SCIM support for license management. The release also adds mobile support for Omni and SMS tasks, MCP connector management and Knowledge Search in the mobile apps, improved buyer and seller tagging in Kaia, and the ability to sync Gong recordings directly into Kaia.

Field reps can manage integrations, read opportunity detail and work SMS tasks from a phone rather than a desktop. Moving connector management onto mobile also moves an administrative control onto a device class that is usually outside a team's endpoint policy, which is worth a look for regulated buyers.