ZoomInfo powers Salesforce Agentforce Prospecting Agent with GTM.AI

ZoomInfo says Salesforce’s Agentforce Prospecting Agent is now generally available with GTM.AI as the context layer behind its account and contact recommendations. The integration gives mutual customers verified contact, company, intent and Scoops data inside Salesforce without a separate enrichment pass or CSV import.

Why it matters: - Salesforce customers using Agentforce now get verified ZoomInfo data inside an autonomous sales agent that can prioritize outreach and explain why each account or contact appears in the queue. - ZoomInfo is positioning verified, continuously refreshed data as the fix for stale prospecting inputs that can create bad outreach at scale. - The integration extends the same GTM.AI infrastructure already used across other AI and sales tools, making the data layer the main differentiator rather than the agent interface.

What happened: - ZoomInfo said the Salesforce Agentforce Prospecting Agent is generally available with GTM.AI powering account and contact recommendations. - The Prospecting Agent runs inside Salesforce and builds a daily prioritized queue of accounts and contacts. - The agent drafts personalized outreach against verified data while reps keep ownership of the conversation, relationship and close. - Mutual customers receive verified contact, company, intent and Scoops data inside Agentforce by default. - The setup removes the need for a separate enrichment pass or CSV import.

The details: - GTM.AI is ZoomInfo’s headless GTM context layer. - GTM.AI exposes ZoomInfo’s verified data graph and agentic orchestration through API and Model Context Protocol. - The GTM Context Graph contains identity-resolved data on 100 million companies, 500 million contacts and billions of signals. - ZoomInfo says the graph is continuously updated and continuously queryable. - A governance plane sits above the graph and applies access control, permissioning, data lineage, AI policy and audit logging across surfaces that consume GTM.AI. - Each queue row includes two cited reasoning columns. - “Why this account” explains the signals behind the account recommendation, including BDR team size, year-over-year growth, technology footprint, CRM activity, funding events, executive moves and active intent. - “Why this prospect” explains why the contact is the right person to reach, combining Salesforce engagement history with GTM.AI signals such as job changes, new champions and intent surges. - Every signal cites its source. - ZoomInfo says about 70% of B2B contact data decays every year. - The company argues that stale data is a bigger risk for autonomous agents because incorrect outreach can scale quickly and damage brand trust. - The integration brings Salesforce customers onto the same data foundation behind HubSpot Breeze, Microsoft Copilot Studio, IBM watsonx Orchestrate, Outreach AI, Gong, LeanData, Glean, Claude and ChatGPT. - ZoomInfo described the Salesforce deal as one of dozens of completed integrations on the same infrastructure.

Between the lines: - The announcement is as much about data governance as it is about automation. - ZoomInfo is trying to make verified context, source tracing and policy controls the core product message for AI sales workflows. - The company is also signaling that agent performance depends less on the model itself and more on the quality of the market data underneath it. - By emphasizing cited reasoning, ZoomInfo is addressing a common enterprise concern: whether AI recommendations can be checked by humans before action is taken.

What’s next: - Salesforce customers running Agentforce can use GTM.AI as the default GTM context layer. - ZoomInfo says early adopter Perk generated 60% of its outbound pipeline in the first two weeks of use. - The company says that metric measures pipeline, not activity, meetings booked or clicks. - ZoomInfo is directing users to learn more and GTM.AI.

The bottom line: - ZoomInfo is betting that AI prospecting wins when verified data, not just automation, sits at the center of the workflow.