Before You Turn On an AI Sales Agent, Look at Your CRM
Salesforce has introduced Hunter by Sales Cloud, an AI outbound sales agent built into Agentforce Coworker. It researches target accounts, drafts personalized outreach and handles follow-ups, using what's in your CRM along with approved outside data. According to the September 11, 2026 announcement, Hunter is in pilot, with general availability planned for November 2026.
Here are the three priorities every team should get right before turning an agent like this on.
1. Tidy up duplicates, departed contacts, and ownership
Salesforce's data readiness trailhead, points out that when a customer's information is split across duplicate records, an agent can't see the whole picture. The good news is you don't need perfect data. Salesforce advises cleaning only what the agent needs.
Build duplicate record reports for Accounts, Contacts and Leads, then merge the obvious ones.
Review your duplicate rules, which can alert or block users who create a likely duplicate. Salesforce turns on standard rules for business accounts, contacts and leads automatically.
Make sure every account in the agent's scope has a clear owner, and flag contacts who have left their company.

2. Look at how outside data flows in
Enriched data helps agents, but where it lands matters. If you use Data Cloud copy field enrichments to bring data into CRM fields, Salesforce warns that mapping one to an existing field overwrites what's there. In Salesforce's own example, a service rep updates a customer's last name, a sync restores the old one, and the new value can't be recovered.
If you use ZoomInfo or Demandbase, set their standard fields to fill blanks only (ZoomInfo calls this ‘Complete if missing’; Demandbase, ‘Update, if blank’). Allow overwrites only on fields created for that vendor.
Send copy field enrichments to their own dedicated fields instead of fields your team edits, as Salesforce recommends.
Trigger ingestion with a flow when those fields change, rather than relying on a schedule.
Turn on field history tracking for key fields to see old and new values and who changed them. It covers up to 20 fields per object and keeps history for 18 months (24 months via the API).

Hunter can also write partner data back to your records, so the same rules apply to the agent’s own updates.
3. Plan a smooth handoff
Salesforce's guidance on agent-to-human handoffs, written mainly for customer service, points out that slow handoffs, and handoffs that make people explain themselves again, cause more people to drop off. Same applies to Sales agent-to-human handoffs. The person taking over should see everything the agent saw.
With Hunter, you can make anything that reaches a customer, like an outreach email or a proposal, wait for a rep's approval, and Hunter keeps a log of everything it does.
That only helps if you've decided who approves what, and how fast. Our recommendations:
Define what counts as a real opportunity, such as a reply or a meeting request.
Name who picks it up and how quickly they should respond.
Decide what the agent stops doing once a prospect replies or a rep takes over, so the prospect never hears from both.
Make sure an opt-out stops the agent immediately and every outreach email has a working unsubscribe link. U.S. anti-spam law (CAN-SPAM) applies to business-to-business email too.

Start small, then scale
Salesforce's advises starting with a focused use case. Pick one segment, clean the accounts the agent will touch, set your data rules and map the handoff. Pilot there, then expand.
At iSight Technology, we help teams do exactly this. If you're planning an agent pilot, let's talk.
Sources:
Demandbase, Manage Demandbase One for Sales Export to CRM Settings.
AI Outbound Sales Agent (Hunter), Salesforce
Salesforce Expands Agentforce With a New Portfolio of AI Agents Built for High-Value Work, Salesforce News, September 11, 2026
Measure Your Data Readiness, Salesforce
Understand Salesforce Capabilities for Reliable Data Readiness, Trailhead
Create Reports on Duplicate Records, Salesforce Help
Manage Duplicates Using Duplicate Record Sets, Salesforce Help
Stop Users from Creating Duplicate Records, Salesforce Help
Enrichment Considerations, Salesforce Help
Field History Tracking Overview, Salesforce Help
Agentic AI Playbook, Salesforce
_edited.png)

Comments