Salesforce Hunter: What to Check Before You Switch It On

In October 2026 the outbound agent moved inside the CRM. Salesforce showed Hunter at Dreamforce, and within days ZoomInfo, Demandbase and Apollo each announced they were flagship data partners. The data now ships with the agent. That changes who decides which provider answers, which signals trigger a touch and who approves the send. This page covers what was announced and the checks to run before you turn it on.

What is Salesforce Hunter?

Hunter is an outbound sales agent for Sales Cloud. Per Salesforce's Hunter page, a rep or team gives it a goal (build pipeline, engage leads, progress deals, prepare the forecast) and it maps the work, runs approved actions and adjusts the plan. It finds accounts and contacts, personalizes outreach, prepares follow-ups and creates and updates opportunities. It is built into Agentforce Coworker and keeps its memory on account, contact and opportunity records.

Status matters for planning. ZoomInfo's October 15, 2026 release says general availability is expected later this year, and Apollo's announcement said Hunter was in pilot with GA planned for November. Salesforce had not published pricing.

Why does a CRM-native outbound agent change your stack?

Hunter is not one vendor's experiment. destinationCRM's Dreamforce coverage (October 16, 2026) names three data vendors that each signed on to supply the same agent. The pattern is the same everywhere: the agent is bundled, and the data calls underneath it are where the decisions and the costs live.

• Provider choice moves to the CRM contract. If reps work through Hunter, the gateway decides which vendor answers first, not your enrichment waterfall.
• The agent acts on signals you did not define. Funding, hiring and intent signals arrive pre-packaged; your ICP rules decide whether they are worth a touch.
• Sends become a configuration setting. Approval is available, not mandatory, so someone has to own that switch.

What should you check before you switch Hunter on?

Five checks, in order. Each one is something you can decide in a working session before the pilot starts, and each one is cheaper to settle before the agent has written to live opportunity records than after.

1. Which provider answers each field?

Pick a set of target accounts you already know well. Run them through Hunter's data and through your current enrichment, then compare email match rate, bounce rate, mobile coverage and title accuracy field by field. Keep whichever source wins per field, and ask Salesforce how provider order is set inside the gateway. A clean CRM is still the starting point; see CRM data quality.

2. Which actions need a human?

Salesforce says customer-facing actions can require rep approval and every action is logged. Turn approval on for every send and every opportunity stage change for at least the first month. Read the logs weekly: what it drafted, what reps rejected and why. Loosen one action type at a time, only once the rejection rate is low and stable.

3. Which signals is it allowed to act on?

A funding round at an account outside your ICP is noise, however fresh. Write down the signals that justify a touch for your buyer (a new revenue leader, a job posting that names your category, a pricing page visit from a target account) and the fit floor an account must clear first. The method is in signal-based selling and Pain-First ICP scoring.

4. Who answers inbound hand-raisers?

Hunter is built around outbound goals. A demo request still needs an owner, an alert and a first touch within minutes, and that path should not wait for an agent's plan to update. Keep speed-to-lead routing separate and measured, and let the agent pick up follow-up after the first human response.

5. How will you know it worked?

Set the baseline before the pilot: meetings booked per rep per week, reply rate, bounce rate, and opportunities created from outbound. Run Hunter on one team or segment and keep a comparable group on the current motion for the same weeks. Vendor case figures are a reason to test, not a forecast; Salesforce's own customer numbers are vendor-supplied.

What if you are not on Salesforce?

The checks still apply, because the same move is happening across the category: agents bundled into the CRM or data platform, with metered data or credits underneath. For a vendor-by-vendor view of standalone tools, see the best AI SDR tools roundup and AI sales agents vs human SDRs. Whatever runs the outreach, the work that decides results is the same: who you target, which signal triggers a touch, how fast inbound gets an answer, and who approves what goes out.

The Outbound System agent builds that signal-to-sequence routing inside your own Claude, whichever tool sends. To see what slow follow-up is costing you now, see your leaks priced in dollars.

Frequently asked questions

Sources and references

• Salesforce, "Meet Hunter, Your New Outbound Sales Agent" (product page and FAQ, 2026): capabilities, Agentforce Coworker, Data Vendor Gateway, rep approval and action logging.
• ZoomInfo, "ZoomInfo Named a Flagship Data Partner for Hunter" (October 15, 2026): data scope, no separate contract, GA expected later in 2026.
• Apollo, "Apollo Named Flagship Data Partner for Hunter" (2026): the seven prospecting actions, pilot status, GA planned for November.
• destinationCRM, "Salesforce Introduces Hunter, a Sales Agent" (October 16, 2026): Dreamforce launch and the Demandbase capability list.