Bahasa Indonesia

What Changes Inside Outreach Before the June 15 Cutover

Outreach just merged ZoomInfo's signal layer into the sequence engine and gave Sales Ops six weeks to migrate off the legacy homepage. The audit window closes June 15.

This isn't a routine feature drop. According to Outreach's May 2026 release notes (covering the May 14 through June 18 rollout window), the platform shipped two changes that require immediate Sales Ops attention: a deep ZoomInfo integration that rewires how signal-triggered sequences work, and a hard deprecation deadline for the legacy 360 homepage that forces every remaining user to migrate before September 30. On top of that, the MCP Server Actions surface now includes write and delete capabilities that didn't exist in February, which raises a new category of agent governance questions.

If your team is running Outreach and hasn't opened the release notes yet, this piece walks through what shipped, why it matters competitively, and the four questions Sales Ops needs to answer before June 15.

What the May 2026 Release Actually Ships

Per Outreach's May 2026 release notes, the release bundles six distinct changes:

20 ZoomInfo Signals in Smart Data Enrichment. Outreach now surfaces 20 new ZoomInfo Signals directly inside agents and sequence workflows, organized into four categories: hiring trends, leadership changes, funding events, and intent signals. The signals pull through the existing Smart Data Enrichment layer, so they appear in the places your reps already work without requiring a separate lookup step or a middleware integration.

Legacy 360 Homepage Deprecation. Starting June 15, 2026, Outreach begins migrating users off the legacy 360 homepage. The replacement is a personalized homepage that adapts its layout and data views to the user's role (seller, customer success, or account rep). Any user still on the legacy homepage after September 30 is automatically migrated. The legacy experience is retired that day.

Custom Object Variables in Sequences. Sequences can now trigger on custom-object data, including events and webinar registrations, and pull personalization fields directly from those custom objects. For teams that track prospect engagement in non-standard objects (product trials, in-person events, certifications), this unlocks trigger logic that previously required workarounds.

Deal Health Score Timing Model. The Deal Health Score now factors in whether a deal is likely to close by its listed close date, not just whether engagement is happening. This shifts the scoring from a pure activity model toward a timing-and-engagement model, which should surface more meaningful risk flags in the days before a close date.

Forecast Movement Customization. Admins can now configure which fields appear in Forecast Movement charts, on a per-forecast basis. This is a smaller change but relevant for Revenue Ops teams that manage multiple forecast categories with different fields.

Expanded MCP Server Actions. AI agents can now create accounts, opportunities, and prospects, delete those same objects, and add or remove prospects from sequences. The February 2026 MCP launch (which we covered in the original Outreach MCP release piece) established the read-and-trigger foundation. The May release adds write and delete, which fundamentally changes the risk profile of any agent workflow running on Outreach.

Key Facts

  • 20 new ZoomInfo Signals now surface inside Outreach sequences, agents, and Smart Data Enrichment across 4 categories: hiring, leadership change, funding, and intent (Outreach, May 2026 release notes)
  • Legacy 360 homepage deprecation runs June 15 through September 30, 2026; after that the personalized homepage is the only option (Outreach, May 2026 release notes)
  • MCP Server Actions expand to create or delete accounts, opportunities, and prospects, plus sequence membership management (Outreach, May 2026 release notes)

Why 20 ZoomInfo Signals Inside Sequences Changes the Outreach-vs-Apollo Math

Until now, one of the clearest arguments for Apollo over Outreach was native enrichment breadth. Apollo's contact and account database feeds its sequence triggers directly. If you wanted Outreach sequences to fire on hiring events, leadership changes, or funding rounds, you typically needed a separate enrichment layer, a webhook, or a ZoomInfo integration sitting outside the sequence engine.

That gap just got smaller. With 20 ZoomInfo Signals embedded in Smart Data Enrichment and surfaced inside sequence workflows, Sales Ops teams running Outreach can now build signal-triggered sequences without a parallel enrichment stack. Hiring at a key account? Signal fires. New CTO confirmed? Signal fires. Series B closed? Signal fires.

This matters for teams that have been doing the Outreach-vs-Apollo evaluation. We covered ZoomInfo's GTM rebrand earlier this year, which already flagged that ZoomInfo's value proposition is shifting toward signal delivery rather than static data. The Outreach integration is the first place that shift becomes tangible inside a sequence workflow.

It also changes the enrichment middleware calculus. If your team pays for a separate enrichment tool primarily to pipe hiring or funding signals into Outreach sequences, that tool's value proposition just got weaker. Sales Ops should audit which enrichment sources currently feed which triggers before assuming the ZoomInfo Signals are redundant or additive.

One caveat: the quality and freshness of ZoomInfo Signals varies by category. Intent signals, in particular, have historically required careful threshold calibration to avoid flooding sequences with low-quality triggers. The 20-signal set includes intent, which means your sequence logic needs to account for signal confidence, not just signal presence.

The 4-Question Sales Ops Audit Before the June 15 Migration Window Opens

The legacy 360 homepage deprecation is the most time-sensitive item in this release. Six weeks is enough runway if you start now. It's not enough if your team discovers on June 14 that three onboarding flows, two custom saved views, and a manager coaching workflow all depend on the legacy layout.

Here's the framework Sales Ops should run before June 15:

The 4-Question Migration Audit

  1. Which legacy 360 workflows have no equivalent on the new homepage? The personalized homepage is role-based, not fully configurable. If you built workflows or saved views that live only in the legacy 360 interface, identify them now. Anything without a clear equivalent on the new homepage needs to be rebuilt or deprecated before the migration runs.

  2. Do the 20 ZoomInfo Signals overlap or replace your current trigger inventory? This question is about sequence cleanup, not just enrichment. If you currently use third-party signals to trigger Outreach sequences, map each trigger against the four new ZoomInfo Signal categories (hiring, leadership change, funding, intent). Eliminate redundant triggers. Keep anything that ZoomInfo doesn't cover.

  3. Which MCP agents currently have write access, and is that intentional now that delete is on the menu? Before May 2026, Outreach MCP agents operated on a read-and-trigger model. Now they can delete accounts, opportunities, and prospects. Any agent that was provisioned under the assumption that write access meant "add to sequence" now has a larger blast radius. Review agent roles before the new actions go live in your environment.

  4. Does the new Deal Health Score timing model change which deals get inspected at your QBR? The shift from a pure engagement model to a timing-and-engagement model means some deals that previously looked healthy (high activity, far-out close date) may now surface as risks if the close date is near and the deal hasn't advanced. Run the new score against your current pipeline before your next QBR so you're not surprised by what surfaces.

These four questions aren't optional paperwork. They're the minimum audit before you're forced to migrate on someone else's timeline.

What MCP Write-and-Delete Actions Mean for Your Agent Governance

The February 2026 MCP launch positioned Outreach's AI agent layer as a productivity tool. Agents could read account data, surface signals, and trigger actions, but they weren't creating or deleting CRM objects. That made the governance conversation relatively straightforward: who can run agents, and what triggers are acceptable?

The May release changes that conversation. As covered in the Salesforce Slackbot and MCP ecosystem piece, the broader MCP ecosystem is moving toward write capabilities across platforms. Outreach's expansion follows the same arc. But write and delete actions on accounts, opportunities, and prospects carry data integrity risk that read-only agent actions don't.

Three governance decisions Sales Ops needs to make before using the new MCP actions in production:

First, define which agent roles are allowed to delete objects versus which can only create or update. Delete should require a higher level of approval or a dedicated agent identity, not the same role used for enrichment or sequence management.

Second, establish a rollback protocol. If an agent deletes a prospect that should have been updated, you need a documented path back to the pre-action state. Most CRMs have soft deletes, but confirm how Outreach handles agent-initiated deletes before you rely on it.

Third, log every agent write action. The value of MCP agents is speed, but speed without a clean audit trail is how data quality erodes. Build logging into the agent workflow now, before the volume of agent writes makes retroactive audit impractical.

For broader context on how AI agents are reshaping the sales tech stack, the Salesforce State of Sales 2026 piece covers the governance patterns emerging across the industry. The Outreach MCP expansion fits the same pattern: agents move faster than humans, so the governance layer has to be built before the agents are deployed at scale.

What to Do This Week

Three specific actions for Sales Ops teams before June 15:

1. Catalogue every workflow built on the legacy 360 homepage. Pull your current saved views, manager dashboards, and custom homepage configurations. Document which ones have equivalents in the new personalized homepage and which don't. Assign owners for anything that needs to be rebuilt. Don't wait for Outreach to migrate you in July and discover the gap then.

2. Dry-run the new ZoomInfo Signal taxonomy on one active campaign. Pick a campaign where you currently use a third-party enrichment signal (hiring event, funding round, leadership change) and map it against the corresponding ZoomInfo Signal category. Check whether the new signal fires on the same accounts, at the same cadence, with comparable data freshness. This is a two-hour test that prevents a surprise sequence overlap when both signals are live simultaneously.

3. Audit MCP write permissions on every agent role in your Outreach environment. List every agent identity that currently has MCP access. Review whether write and delete permissions have been added automatically with the May release or require explicit provisioning. If write access is default-on, scope it down before your agents run. You want intentional delete capability, not accidental delete capability.

The Deal Health Score change doesn't require immediate action, but before your next QBR, run the new timing-and-engagement score against your current pipeline and compare it to the previous engagement-only score. The delta will tell you whether the new model surfaces different risks.

For teams evaluating deal intelligence more broadly, the HubSpot Spring 2026 deal progression piece covers how deal health scoring is evolving across platforms, which gives useful context for interpreting Outreach's timing model change.

FAQ

What is the deadline for migrating off the Outreach legacy 360 homepage?

The migration window opens June 15, 2026. Outreach will begin moving users to the personalized homepage during the June 15 to September 30 window. Any users still on the legacy 360 homepage after September 30 are automatically migrated, and the legacy experience is retired permanently at that point. Sales Ops teams should complete their own migration audit before June 15 to avoid being moved on Outreach's schedule rather than their own.

How do the 20 new ZoomInfo Signals work inside Outreach sequences?

The signals are delivered through Outreach's Smart Data Enrichment layer and surface inside existing agents and sequence workflows without requiring a separate integration. They cover four categories: hiring trends, leadership changes, funding events, and intent signals. When a signal triggers, it surfaces in the workflow context where your reps and agents already operate, rather than requiring a manual lookup or a third-party middleware connection.

Do the new MCP Server Actions require separate provisioning in Outreach?

According to Outreach's May 2026 release notes, the expanded MCP Server Actions include the ability to create or delete accounts, opportunities, and prospects, and to add or remove prospects from sequences. Sales Ops teams should audit their current agent role configurations to determine whether write and delete capabilities have been enabled automatically or require explicit provisioning. Given the data integrity risk of delete actions, it's worth confirming the default state before agents run at volume.

Should we replace our existing ZoomInfo or enrichment integration now that Outreach has ZoomInfo Signals built in?

Not immediately. The 20 ZoomInfo Signals cover four categories, but your existing enrichment layer may cover additional signals or data points that the built-in integration doesn't. The right approach is to map your current trigger inventory against the four ZoomInfo Signal categories and identify where there is genuine overlap versus where your existing enrichment covers gaps the new signals don't address. Replace what's redundant; keep what's additive.

Source: Outreach May 2026 Product Release Notes.