How to Configure Agentforce Prospecting Agent for Real Sales Prospecting?

Table of Content

Author

Vishal Soni
Vishal Soni

Date

Vishal Soni
Jun 23, 2026

How to Configure Agentforce Prospecting Agent for Real Sales Prospecting?

You completed the setup wizard. You connected to ZoomInfo. You assigned the agent to an account record and clicked Generate Prospects from Account. Nothing happened. No errors. Just silence.

This is the experience most practitioners hit when they deploy Salesforce's Agentforce Prospecting Agent for the first time, not because the agent is broken, but because the configuration gap between the wizard and production-ready behaviour is real and undocumented.

Salesforce announced the Agentforce Prospecting Agent as part of its April 2026 Sales Cloud release. They positioned it as an always-on prospecting partner that autonomously researches target accounts, qualifies them against your ICP, and surfaces ranked prospects directly in CRM. The pitch is compelling, and having now built and tested this in a live org, I can confirm the capability is real.

But getting there took more than following the setup wizard. This blog documents the configuration gotchas, the architectural decisions that matter, and the specific things you need to get right before a single prospect shows up.

Step-by-Step Guide to Configure Agentforce Prospecting Agent

This guide walks through the key setup steps required to get the Agentforce Prospecting Agent working in Salesforce. It covers the org requirements, account report setup, ZoomInfo connection, Agentforce Builder updates, ICP configuration, and the checks needed before running your first prospect generation test.

Step 1: Confirm SDO Availability Before Anything Else

If you're working in a Salesforce Developer Org (SDO) and can't find the Prospecting Agent template, you're not imagining things. The agent is not available on older SDOs. You need a recently provisioned org that falls within the April 2026 release window.

If your SDO predates that window, spin up a new one before troubleshooting anything else. Time spent debugging a missing feature flag on an old org is time wasted.

Step 2: Configure the Accounts Report — Keep It Simple

During configuration, the wizard asks you to point to a Salesforce Accounts report. This report defines the universe of accounts the agent is allowed to work on.

Recommendation: Create a fresh, unfiltered Accounts report with no criteria applied. This gives the agent access to your full account base. If your use case requires narrower scope: a specific territory, segment, or account tier and build those filters into the report.

A clean, unfiltered Accounts report used as the agent's account source. The selected account must appear in this report for the agent to run.

One important point: the selected account must be present in this report for the agent to run on it. If someone clicks "Generate Prospects from Account" on a record not included in the report's result set, the agent will not execute, no error, just silence.

Step 3: Complete the Setup Wizard — Then Go Further

The official Salesforce Help documentation walks you through a four-step configuration wizard: Getting Started, Add Sources, Assign Prospects, and Tools and that's where you handle most of the structural setup: connecting ZoomInfo, specifying the account source report, and assigning the agent.

The final "Tools" step of the Setup Wizard showing ZoomInfo connected. Completing this wizard is the start, not the finish.

But here's what's not obvious: after completing the wizard, you still need to open Agentforce Builder and manually edit the sub-agent instructions. The wizard doesn't surface the Account Research qualification criteria or the Prospect Finder ICP configuration inline. You have to navigate into the agent's topic/sub-agent structure and modify those instructions directly. 

If you skip this step, the agent runs with default logic that may not match your use case at all.

ZoomInfo: The Free Trial Is Enough to Start

You don't need a full ZoomInfo enterprise contract to test this. A ZoomInfo free trial (the Lite variant) is sufficient for basic account enrichment and contact lookups, which covers the core Prospecting Agent workflow. For a demo or proof-of-concept, this gets you far enough to validate the end-to-end flow before committing to licensing.

The Three-Layer Architecture You Need to Understand

The Prospecting Agent isn't a single monolithic agent, it has three distinct sub-agents, each playing a specific role in the reasoning chain. Understanding this architecture is essential because when something doesn't work, you need to know which layer to tune.

Three sub-agents of Prospecting Agent

1. The Router

This is the entry point. When the agent is invoked from an account record, the Router sub-agent takes the initial context and classifies whether to route execution toward Account Research or Prospect Finder. It's analogous to a topic classifier in a standard Agentforce setup and like topic classifiers, its behavior is sensitive to the instructions you give it.

2. Account Research

This sub-agent performs account-level qualification. It takes the selected account, cross-references it against your connected data sources (ZoomInfo being the primary one), and evaluates whether the account passes your Qualification Criteria.

The out-of-the-box Qualification Criteria defaults to: Account must be in the Technology industry. This is checked against both the Salesforce Account Industry field and enrichment data from ZoomInfo (industry, primarySubIndustryCode, industries fields).

There are also Nice-to-Have Criteria: Signals like recent funding rounds, product launches, or market expansion news, which are used to prioritize and enrich the agent's reasoning, but they do not act as hard filters. An account can still pass qualification even if it doesn't meet these signals.

The default Qualification Criteria in Account Research, to be updated to reflect your actual ICP before even testing to fetch your first prospect.

Key action required: You almost certainly need to change these default criteria to match your actual ICP. Leaving the defaults in place means the agent will apply Technology industry logic regardless of your business context.

3. Prospect Finder

Once an account is qualified, this sub-agent identifies individual prospects at that account. It applies your ICP criteria: job title, seniority, function, to ZoomInfo's contact database and returns matching individuals. The default ICP criteria are generic placeholders. You must update these to reflect your real target persona.

The Prospect Finder sub-agent, where updates would be required to specify your ICP Criteria.

Triggering the Agent: The “Generate Prospects from Account” Button

Once setup is complete and the agent is active, a "Generate Prospects from Account" button appears on the Account record page layout. Clicking it opens a modal where you select the agent, assign prospects to a user, and set a maximum prospect count (default is 5).

The "Generate Prospects from Account" modal. Select the active agent, assign the owner, and set a maximum prospect count before triggering the run.

After you click Generate, the agent runs asynchronously. You'll receive a notification once the process completes.

Success notification confirming prospects were generated for the selected account.
The Account record page after a successful run, showing the "Generate Prospects from Account" button in the top-right action bar.

In practice, expect anywhere from 10 to 60 seconds and in some cases, you may need to re-trigger the process if results don't appear immediately. This seems to be a timing/latency issue rather than a configuration problem; a second attempt on the same account often succeeded where the first didn't.

The Three Conditions That Must All Be True

This is the most important thing I can tell you. After all the setup is done, the agent will silently fail to produce prospects unless three conditions are simultaneously true:

  • The account appears in your configured Salesforce report. The agent won't even start if the record isn't in scope.
  • The account meets the Qualification Criteria in the Account Research sub-agent. If your industry, firmographic, or signal criteria aren't satisfied, the agent stops here, no contacts will be returned.
  • ZoomInfo has matching prospects for that account that satisfy your Prospect Finder ICP criteria. Even a fully qualified account returns zero prospects if ZoomInfo has no contacts at that company matching your persona definition.

For your initial testing, pick an account you know is a real technology company with real employees in ZoomInfo, and confirm it meets whatever criteria you've defined. Also worth noting: don't try to run this on Partner accounts or Person Accounts. The agent is designed for standard B2B customer accounts only.

What Good Output Looks Like

When everything is correctly configured, the New Prospects queue populates with a list of contacts, each accompanied by a "Why This Prospect?" explanation. The agent provides per-prospect reasoning, explaining which qualification criteria were met, which nice-to-have signals were present, and where the data came from.

The New Prospects queue showing ranked prospects with "Why This Prospect?" reasoning, Approve/Reject actions, and the Insights panel surfacing the agent's full logic per prospect.

The result is a reviewable list with Approve/Reject actions per prospect, and a full Insights panel on the right that surfaces the agent's reasoning in plain language. From an architecture perspective, this transparency is genuinely useful, reps aren't accepting a black-box recommendation; they're seeing the logic and can calibrate their trust in the output.

Summary Checklist

Use this as a go/no-go reference before your first live test run:

Check What to Do
SDO age Use a recently provisioned org — old SDOs don't have this feature
ZoomInfo connection Free trial (Lite) is sufficient for testing
Accounts Report Create a fresh, unfiltered report; add filters only if needed for scope
Account Research Update Qualification Criteria to match your actual ICP
Prospect Finder Replace default ICP persona with your real target job titles/seniority
Test account selection Choose a real company in ZoomInfo matching all three conditions
Account type Standard customer accounts only — not Partner, not Person Account
Timing Allow 10–60 seconds; retry if the queue doesn't populate on first attempt

Conclusion

The Agentforce Prospecting Agent can do a lot. But completing the setup wizard is not enough.

Three prerequisites need to align, one key Agentforce Builder step is easy to miss, and the default ICP criteria must be updated before the first run. Miss any of these, and the agent may look ready while doing nothing.

These configuration choices decide whether you see results on day one or spend weeks troubleshooting.

At MIDCAI, we help teams get it right, from agent configuration and ICP design to ZoomInfo integration.

Planning this for your Salesforce org? Let’s talk.

No items found.

About the Author

Vishal Soni

With 17+ years in data, AI, and tech consulting, I’ve worked with pioneers from IBM to IIT Kanpur. Joining MIDCAI marks a fresh chapter - where deep thinking meets meaningful execution, and curiosity leads the way in blending AI, cybersecurity, and human-centered consulting.

Similar Blogs

Ready to future-proof your business?

Get in touch with us for any enquiries and questions

Get in touch

Define your goals and identify areas where technology can add value to your business

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Join minds that move technology

We are looking for passionate people to join us on our mission.

Let’s build what’s next

where your skills fuel innovation and your growth powers ours

Salesforce Technical Lead
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Let’s work through it together.

CRM services that bring your data, teams, and

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.