Summer '26: Qualify Contacts and Person Accounts With Agentforce

By John Harris · 2026-07-15

Introduction

The Salesforce Summer '26 release includes a small but genuinely useful upgrade to Agentforce for Sales: AI-driven qualification is no longer limited to Leads. Your agents can now qualify Contacts and Person Accounts as well.

Until now, Agentforce could only assess prospects that existed as Lead records. If a promising individual lived in your org as a Contact - or as a Person Account in a B2C setup - the agent simply couldn't evaluate them. For organizations with mature Sales Cloud implementations, where a large share of the addressable market already sits on Contacts and Person Accounts, that meant Salesforce AI qualification covered only part of the real pipeline.

Summer '26 closes that gap. In this article, we'll walk through what's new, why it matters for your sales process, and how to switch it on - based on the official Salesforce Release Notes.

What's New?

With Agentforce for Sales, qualification now extends beyond the Lead object. Lead Generation Agents and Lead Nurturing Agents can work across a broader set of records, which means they can now qualify:

  • Leads - the classic entry point for new prospects, exactly as before.

  • Contacts - people who already exist in your database, typically associated with business Accounts.

  • Person Accounts - the record type used when the individual is the customer, common in B2C and hybrid models.

The qualification logic follows the same principle as before: the agent assesses how strong a prospect is based on the conversation and on how closely that person matches your Ideal Customer Profile (ICP). What's changed in Salesforce Summer '26 is where that logic can be applied - the agent can now qualify prospects wherever they actually live in your CRM.

The outcome is broader qualification coverage and stronger pipeline management, without forcing you to reshape your data model around a Lead-only tool.

Why This Matters

Lead Qualification has long been one of the most practical applications of Salesforce AI: let an agent handle the early conversation, work out whether someone deserves a rep's attention, and pass along only the promising ones. The limitation was scope. Real-world pipelines rarely consist of Leads alone:

  • Many orgs convert Leads early, so most working relationships live on Contact records.

  • B2C and hybrid businesses model their customers as Person Accounts from day one.

  • Account-based selling targets known people at named accounts - Contacts by definition.

  • Expansion and cross-sell conversations happen inside the existing customer base, not in the Lead queue.

Extending qualification to these records delivers concrete business value:

  • Better qualification - every prospect conversation can be assessed, regardless of record type.

  • Improved ICP matching - the agent evaluates fit against your Ideal Customer Profile across Leads, Contacts, and Person Accounts alike.

  • Better pipeline visibility - qualification insight becomes available across more of your pipeline, not just at the very top.

  • Higher productivity - reps spend less time sifting through records and more time focusing on high-potential deals.

  • Support for account-based selling - qualification finally works with the records that account-based teams actually use.

  • A better fit for mature CRM implementations - established orgs with years of Contact data benefit the most.

A couple of practical examples. Imagine an inbound team where a returning Contact - someone who downloaded a whitepaper last year - starts a new conversation. Previously, a rep had to triage that interaction manually, or the person ended up duplicated as a fresh Lead. Now the agent can qualify the Contact directly. Or take a B2C company running on Person Accounts: its Lead Nurturing Agent can finally evaluate the very records that represent its actual customers and prospects.

How It Works

Agentforce evaluates the conversation itself to determine qualification. As the agent engages with a prospect, it assesses how strong that prospect appears based on what is discussed and how closely the person matches your Ideal Customer Profile. Promising opportunities are surfaced to your sales team earlier, so reps spend less time reviewing records that were never going to convert.

It's worth stressing that Summer '26 doesn't introduce a brand-new qualification engine. It extends the existing Lead qualification capability that Lead Generation Agents and Lead Nurturing Agents already use, and applies it to Contacts and Person Accounts. If you're familiar with how your agents qualify Leads today, the behavior will feel consistent - the difference is the set of records in scope.

How to Configure It

Enabling the feature is a quick, declarative change handled through Salesforce Go:

  1. Open Salesforce Go.

  2. Open the Agent setup for Inbound Lead Generation or Lead Nurturing.

  3. Navigate to the Qualification section.

  4. Select which objects the agent can qualify: Leads, Contacts, and Person Accounts.

Because you select the objects individually, you can roll the capability out in stages. For example, keep qualification on Leads only while your team validates the agent's behavior, then add Contacts once you're confident - and Person Accounts if your org uses them. As with any new release feature, it's sensible to review the setup in a sandbox first and to agree with sales operations on which objects should be in scope, particularly where Contacts are shared across teams with different processes.

Best Use Cases

This enhancement is broadly useful, but a few scenarios stand out:

  • B2B sales - qualify Contacts at target Accounts instead of forcing every new conversation through the Lead object.

  • Existing customer expansion - assess upsell and cross-sell interest from people who are already in your CRM.

  • Account-based marketing (ABM) - align AI qualification with programs that work from named Contacts at named Accounts.

  • High-volume inbound sales - let agents triage large volumes of inbound conversations, whichever record type each person maps to.

  • Enterprise sales teams - large orgs with years of Contact and Person Account data can finally point Salesforce AI at that history.

Final Thoughts

The Salesforce Summer '26 release is full of incremental improvements, and this is one of those changes that looks minor on paper but maps directly onto how sales teams actually work. Pipelines are built on Leads, Contacts, and Person Accounts together - so qualification should cover all three. By extending Agentforce in this way, Salesforce has removed an artificial boundary between its AI capabilities and real-world CRM data.

If you're a Salesforce Admin or Consultant, add this to your release review checklist: open Salesforce Go, look at your Inbound Lead Generation and Lead Nurturing agents, and decide deliberately whether Contacts and Person Accounts should be enabled for qualification in your org. For teams running account-based selling or sitting on a mature Sales Cloud implementation, this is likely one of the quickest wins in the entire release. And as always, the official Salesforce Release Notes are the best place to confirm the details before you roll anything out, including which add-on licenses your users need.

Is this on the Agentforce Sales Consultant exam?

Not yet. The Agentforce Sales Consultant exam guide says its questions align to the Summer '25 release, so a Summer '26 feature like this isn't in scope. If you're preparing for that exam, our Agentforce Sales Consultant practice course follows the current guide, with every option explained.

Sources

More articles