Agentforce for Sales
Agentforce for Sales is the Salesforce Agentforce SKU that ships two pre-built agents grounded in Sales Cloud data: the Sales Development Representative (SDR) Agent and the Sales Coach.
Definition
Agentforce for Sales is the Salesforce Agentforce SKU that ships two pre-built agents grounded in Sales Cloud data: the Sales Development Representative (SDR) Agent and the Sales Coach. The SDR Agent handles inbound and outbound prospecting (researching accounts, drafting first-touch emails, qualifying leads, proposing meeting times). The Sales Coach reviews opportunities in flight and gives reps next-best-action coaching tied to the deal's stage, history, and signals.
Both agents run on the Atlas Reasoning Engine and use Agent Actions that read and write Sales Cloud records (Account, Lead, Opportunity, Contact, Task, Event). They ship with standard topics admins can customize: Account Research, Meeting Prep, Opportunity Health, Email Drafting, Pricing Questions. Agentforce for Sales is licensed per conversation, not per user, so the cost model scales with activity rather than seat count.
Why Agentforce for Sales is two agents, not one
The SDR Agent and the Sales Coach in one SKU
The SKU bundles two agents with different jobs. The SDR Agent is conversational and outbound-leaning. A rep or a prospect can ask it to research a company, summarize a contact's recent activity, draft a cold email tied to a recent product launch, or propose three meeting times that respect the rep's calendar. The Sales Coach is more passive. It runs on a schedule against open opportunities, surfaces health concerns, and prompts the rep with a specific suggestion (call the economic buyer, escalate the legal review, update the next step). The two agents share infrastructure (Atlas, topics, actions) but their starter topic sets are distinct.
Sales Cloud data the agents read by default
Out of the box the agents have access to standard Sales Cloud objects: Account, Contact, Lead, Opportunity, OpportunityContactRole, Task, Event, Campaign, Pricebook2, Product2, Quote, and Order. The shipped Agent Actions pull common fields from each object. Custom fields are not read unless you extend the actions or build new ones. The SDR Agent also reads activity history (calls, emails logged via Einstein Activity Capture) when present. Without Einstein Activity Capture or a similar activity sync, the agent only sees activities manually logged by reps, which is usually a small fraction of what actually happened.
Pre-built topics and what they cover
The SDR Agent ships with topics like Account Research, Contact Research, Lead Qualification, Meeting Scheduling, and Email Drafting. The Sales Coach ships with Opportunity Health, Deal Risk, Next Best Action, and Stage Coaching. Each topic has a classification description and three to six attached actions. Most teams keep three or four topics unchanged and customize one or two heavily. The Email Drafting topic is the most-customized in practice because brand voice and product positioning vary by company, while Account Research and Meeting Scheduling tend to work out of the box.
How the SDR Agent drafts outbound emails
The Email Drafting topic invokes a Prompt Template action that pulls the contact's title and industry, the account's recent news (from Einstein Account Insights if licensed), the product the rep is pitching, and any prior conversation history. The template asks the model to draft a three-paragraph email with a specific call to action. The draft is returned to the rep for review. The agent never sends the email itself in the default configuration. A rep can ask the agent to revise tone, length, or hook, and the model regenerates against the same data. The draft writes to a Task linked to the contact when the rep accepts it.
Sales Coach signals and the trigger model
The Sales Coach evaluates opportunities on a schedule (hourly for active deals, daily for the long tail) and against event triggers (stage change, close date push, activity gap). Signals include: no activity logged in 14 days, stage age over 1.5 times the average for that stage, single-threaded (only one contact role), close date in the past with no resolution, and amount changed by more than 25 percent. When a signal fires, the coach generates a specific suggestion ("call your economic buyer at Acme; last contact was 19 days ago") and posts it to the rep through the Agentforce panel or a Chatter feed item, depending on configuration.
Customizing vs accepting the defaults
Most teams underestimate how much of Agentforce for Sales works out of the box. The standard topics for Account Research and Meeting Scheduling are well-tuned and rarely benefit from customization. Email Drafting benefits enormously from custom prompt templates that encode brand voice. Sales Coach signals can be reweighted per segment (an enterprise deal with no activity for 14 days is normal; a transactional deal with the same gap is dead). The right pattern is to ship the defaults to a small pilot, observe the Plan Trace for two weeks, and customize only the topics where the trace shows misfires.
Licensing, conversation pricing, and ROI math
Agentforce for Sales is sold by conversation, not by seat. A conversation is one user-initiated session that can span multiple turns and actions. The Sales Coach counts each scheduled run as a conversation when it produces a suggestion. List price has run around $2 per conversation in 2026 with volume discounts at higher tiers. The ROI conversation usually centers on time saved per rep per week (an SDR who saves three hours of research time per week against a 200-rep team) rather than direct revenue lift, because the agent's contribution to closed-won is hard to isolate.
How to roll out Agentforce for Sales without overwhelming reps
The honest rollout sequence is: license, pilot one topic with one team, observe, expand. Skipping the pilot phase produces the same outcome every time, which is a SKU that gets turned off in month two when the executive sponsor moves teams.
- Confirm prerequisite licenses and data hygiene
Agentforce for Sales needs Sales Cloud Enterprise or Unlimited, the Agentforce add-on SKU, and a clean activity data source (Einstein Activity Capture is ideal). Without activity data, the Sales Coach has nothing to evaluate.
- Enable Agentforce in Setup
Setup, Einstein, Agentforce, Enable. Accept the legal terms. Provision the SDR Agent and Sales Coach from the agent gallery. Both agents land in Agent Builder as editable copies of the shipped templates.
- Pilot with one team and one topic
Pick five to ten reps and one topic, usually Account Research or Meeting Scheduling. Limit access via permission sets so the rest of the org does not see the agent until the pilot finishes.
- Customize the Email Drafting prompt template for your voice
The shipped template is generic. Add three to five lines that describe brand voice, common product hooks, and the desired closing CTA. Test against ten real prospects in the pilot team's pipeline.
- Wire the Sales Coach signals to a Chatter feed item, not just the panel
Most reps live in their email and pipeline view, not the Agentforce panel. A Chatter post on the opportunity makes the coaching visible where reps already work.
- Review the Plan Trace and Testing Center weekly for two weeks
Look for topic misfires, irrelevant suggestions, and template regressions. Adjust topic classification descriptions before adding more actions.
- Expand topic by topic, not team by team
Once one topic works well, roll it to the next team before turning on a second topic. The combinatorial debugging of two new topics on two new teams is what kills most rollouts.
Which of the two shipped agents (SDR, Sales Coach) are enabled. Most teams roll out one at a time.
Permission-set-gated access to the agent. Critical during rollout so the rest of the org does not surface unvetted output.
The customized prompt that encodes brand voice and product positioning. Highest-leverage customization in the SKU.
Per-signal sensitivity for the coach. Allows enterprise vs transactional deals to have different thresholds.
Where Sales Coach suggestions surface: Agentforce panel, Chatter feed, or both. Chatter usually wins on adoption.
- Sales Coach without Einstein Activity Capture or a similar activity sync is mostly silent. Reps' manually logged activity is too sparse for the signal model.
- The Email Drafting topic without customization produces generic email. Reps reject it after two days and turn the agent off in their head.
- Conversation pricing surprises orgs that did not estimate volume. A 200-rep team querying the agent five times a day produces 25,000 conversations a month.
- Custom Sales Cloud fields are not visible to the shipped actions. The agent will not see your custom Account.AccountTier field unless you extend the action.
- Field-level security and sharing rules apply. The agent only sees data the calling user can see, so a manager asking about their team sees more than an individual rep on the same query.
Trust & references
Straight from the source - Salesforce's reference material on Agentforce for Sales.
- Agentforce for SalesSalesforce Help
- SDR AgentSalesforce Help
- Sales CoachSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What kind of solution is Agentforce for Sales?
Q2. Which of these is a typical Agentforce for Sales use case?
Q3. How is Agentforce for Sales grounded and governed?
Discussion
Loading discussion…