Salesforce Hunter Is Due in November

What to prepare before rolling out an AI sales agent

Salesforce has announced November 2026 general availability for Hunter, its new outbound sales agent. As of 9 October, it remains in pilot. Businesses using Salesforce have a useful window to prepare a sales process before committing to a rollout.

Think about a quotation that went quiet after the first meeting. The account owner is busy, and the opportunity stays open until someone asks about it in the monthly review. Start with that problem when evaluating sales AI.

Hunter appeared in Salesforce’s September Agentforce announcement. Our recommendation is to choose one repeatable workflow, agree what the agent may do, and establish how you will measure the result.

What Salesforce Hunter is designed to do

Salesforce describes Hunter as an agent that works towards sales goals over weeks or months. Its advertised capabilities include prospect research, outreach, opportunity updates and pipeline reviews. It learns from CRM history, customer conversations, sales content and seller activity, with approved external data adding context.

A team could delegate follow-up work while keeping a seller responsible for the relationship. That requires a clearer definition of a good next step than “send another email”.

Salesforce’s 28 September Dreamforce recap highlights agents that retain context across sessions. The practical question is whether they can keep a useful sales process moving over time.

What is available now and what is still coming

These published statuses come from the Agentforce announcement and Dreamforce recap, checked on 9 October. GA means generally available.

Salesforce’s Hunter webinar page says it launches in Agentforce Coworker, with Slack, Teams and Claude to follow. Confirm the interface your team needs and the features your contract includes before planning a rollout.

Start with the sales delay you can actually measure

Imagine a distributor with quotations that have had no recorded activity for two weeks. Some buyers are still interested. Others have changed their requirements or already bought elsewhere.

A proposed workflow could review those opportunities, identify missing information, prepare a relevant follow-up and suggest a next step for the account owner. The seller would review customer messages before they are sent. Exceptions, such as a pricing dispute or an unresolved service complaint, would go straight to a person.

Define success before selecting features. For this scenario, track how many eligible opportunities receive a useful follow-up, how many buyers respond, and how much correction time sellers spend. Check whether meetings lead to accepted opportunities and later revenue.

A larger email count alone tells you little about sales quality.

Make the sales process clear enough to delegate

Review a small sample of recent won and lost deals. Can someone understand why each deal progressed, what the buyer needed and who owned the next action? If that information exists only in a salesperson’s memory, make it part of the process before expecting an agent to use it.

For the selected workflow, agree the required CRM fields, the meaning of each opportunity stage and the conditions for stopping follow-up. Remove duplicate contacts and reconcile ownership. Keep approved product information and current pricing easy to identify.

If stock, credit limits or delivery dates live in Odoo or another ERP, decide how that information will reach the workflow and how fresh it must be. A useful sales recommendation may depend on operational data outside Salesforce. Include that dependency in your business system integration plan.

Set approval rules before the first customer message

Salesforce’s Hunter product FAQ says it follows configured permissions and business rules, can require rep approval for customer-facing actions, and logs its actions. Those controls still need deliberate configuration.

For a first pilot, we recommend allowing research and draft preparation while requiring review of outbound messages and proposals. Keep discount decisions, credit commitments and delivery promises with the responsible employee. Define when the agent should stop, escalate or hand an opportunity back to its owner.

Test an opted-out contact, a duplicate account and a deal with an unresolved complaint. The person leading the pilot should be able to see what happened and pause the workflow if it behaves incorrectly.

Budget for the complete workflow

The current Agentforce pricing page offers consumption-based options and per-user licensing. Your organisation will need a Hunter quote for its proposed use case.

Ask which licences and usage charges apply to the exact actions you want. Include the cost of preparing data, connecting systems, configuring approvals and maintaining the workflow. Confirm any allowances, limits and renewal terms in your proposal.

Then compare the total pilot cost with measurable gains: seller time saved after corrections, improved follow-up coverage, and qualified opportunities created or recovered.

Keep the pilot small enough that someone can inspect the results. You need evidence from your own sales process before expanding the spend.

Use October to prepare a focused pilot

We suggest a four-week preparation schedule, adjusted to your team’s capacity and product access.

1. Week 1: Select one workflow and one accountable sales manager. Record current response times, follow-up coverage and the quality of the outcomes.
   
   

2. Week 2: Prepare the relevant records and approved content. Resolve ownership, access and any ERP data dependencies.
   
   

3. Week 3: Write the approval and escalation rules. Review representative examples with your Salesforce team and confirm product access, rollout dates and commercial terms.
   
   

4. Week 4: Test with available capabilities or an authorised pilot, keeping customer actions under review. If Hunter access is not available, use this week to finish test cases and acceptance criteria.
   
   

Expand only after the workflow handles ordinary work and exceptions reliably, and the results justify its cost.

Bring one sales workflow to Symake

Hunter’s planned November release gives Salesforce customers a reason to review how follow-up work gets done. The useful starting point is a process with a named owner, reliable information and a result you can measure.

If your team is considering Salesforce AI, bring Symake one workflow that regularly stalls. We can discuss the CRM setup, integration needs and approval rules required to evaluate it.

Talk to Symake about your Salesforce requirements.

Frequently asked questions

What is Salesforce Hunter?

Hunter is Salesforce’s new AI sales agent, designed to coordinate work across prospecting and the sales pipeline over time. A company configures the rules and approvals under which it operates.

Is Hunter generally available yet?

As of 9 October 2026, Salesforce lists Hunter as being in pilot, with general availability planned for November 2026. Confirm current access and timing before scheduling a launch.

Does an existing Salesforce subscription include Hunter?

Do not assume inclusion. Ask Salesforce to confirm the required edition, any add-ons and the charging model for your proposed workflow. General Agentforce pricing is not a substitute for those terms.

What should a business prepare first?

Choose one recurring sales task, assign its owner and document the expected result. Then prepare the relevant CRM records, approvals and connected data before testing an agent on that task.