Salesforce · Agentforce Sales

Agentforce Engagement

An autonomous prospect-nurturing agent that, once a lead, contact or person account is assigned to it, drafts and sends initial outreach and nudge emails, replies to prospect messages, answers product questions from an uploaded data library, returns meeting links from the prospect owner's calendar and sets the prospect's email opt-out field on request.

Recorded characteristics

Function
Salesforce documents Agentforce Engagement (previously named Agentforce Lead Nurturing, and before that Agentforce SDR / Sales Development Agent) as one evolving agent template rather than several capabilities. Prospects are assigned to the agent by assignment criteria in the Engagement Rules, by an automated action, or by a sales user using the Assign to Agent action; the record owner does not change. Once a prospect is assigned, Salesforce states the agent begins working the prospect immediately and schedules the first email to be sent within an hour, drafting the initial outreach email from the lead, contact or person account record and sending it to the address on the record without delay. If the prospect does not reply within the configured Time Between Attempts, the agent drafts and sends nudge emails until the prospect replies or the configured Maximum Attempts is reached, disengaging three days after the final nudge. When a prospect replies, the agent interprets the reply: a product question is answered using the uploaded data library and the answer email includes a meeting link; an off-topic reply receives a generic reply that copies the prospect owner before the agent disengages; an interested reply receives a reply containing a link to book a meeting with the prospect owner; a meeting request receives a follow-up email offering meeting times based on the prospect owner's calendar, copies the prospect owner and hands the prospect off. If the prospect asks not to be emailed again, the agent sets the prospect's Email Opt Out field to True, stops sending and disengages. The agent adds the prospect to a dedicated Sales Engagement cadence used to plan and track outreach, and its email activity appears in the prospect's Activity Timeline. Salesforce's current modular architecture consists of the Initial Outreach, Follow-up Outreach, Generic Response, Meeting Response, Product Q & A and Manage Opt-Out subagents using the Get Record Details, Return Calendar Link, Answer Questions with Knowledge and Opt Out Target actions; a legacy architecture created before 7 October 2025 used separate draft actions and an explicit Schedule Email action. Agentforce Lead Generation, Agentforce Qualification and Agentforce Sales Coach are documented as separate agents and are not part of this record.
Data access
Salesforce documents the agent using lead, contact and person account record details to personalise outreach, the prospect record owner (owner field must be populated before assignment), the Sales Engagement cadence state for the prospect, and an uploaded data library of business documents through the Answer Questions with Knowledge action. Product and service literature is uploaded in Setup or Agentforce Builder; the Engagement Agent permission set includes View Knowledge and Allow View Knowledge. Einstein Activity Capture governs email content access: with the Header-only Email Capture setting on, Salesforce states the agent cannot use the email subject or body to understand prospect intent or personalise responses, and leaving it off allows the agent to use the full content of the emails. Data 360 is documented as providing auditing, feedback, the Einstein Trust Layer, retrieval-augmented grounding and analytics, and a Data Cloud Admin permission is required to set up data for the agent. For group meeting scheduling, Salesforce states that permission must be given for Salesforce to view free/busy time on Gmail and Outlook calendars, and that the agent shows the combined availability of Inbox users in the group; broader calendar content access is not established. No general access to all CRM or Data 360 data is established by this documentation.
Actions
Can take actions
External actions
Yes
Human confirmation
Conditional
Permission basis
Mixed
Administrative control
An administrator turns on Agentforce Engagement in Setup via Salesforce Go (Agentforce for Sales tile, Agentforce Studio, then the Engagement toggle), which also turns on Automated Actions, Einstein Activity Capture, Email Productivity and Engagement. Agents are created and edited only in Setup or Agentforce Builder; Salesforce warns against deploying them with change sets or metadata. Documented controls include prospect assignment criteria in the Engagement Rules, Time Between Attempts, Maximum Attempts, maximum number of replies, the Send as Seller option, the Require Manual Approval / Review Before Send option, meeting owner (user or group) selection, an optional Qualification setting, agent instructions, subagents, actions and prompt templates, the data library, the agent user record and its connected email account, and permission assignment (Use Engagement Agent, Configure Engagement Agent, Data Cloud Admin). Users can cancel an outreach from an email task in the Activity Timeline, and managers can cancel or retry outreach from the Agent Control Center. Up to 20 sales agents can be added by default.
Default state
Disabled
Availability
Salesforce Help documents Agentforce Engagement as generally available, not as a pilot or beta: Available in Lightning Experience in Enterprise, Performance and Unlimited editions. The Agent Analytics Tableau dashboard for the agent is separately labelled Beta. Salesforce states that Agentforce Engagement does not work if Activity 360 Reporting is turned on.
Licensing
Salesforce Help states the requirement inconsistently across current pages: some pages say "with Sales and Einstein for Sales" and others say "with Sales and the Agentforce Engagement add-on". Engagement agents consume units of Conversations, tracked in Salesforce Digital Wallet, with each Conversation consuming Einstein Requests when it accesses the LLM; one Conversation is consumed when the initial email is sent and covers subsequent activity for that prospect. No pricing is recorded.
External model or provider
Not established
Limitations and uncertainty
Salesforce does not name a specific model or provider for this capability; only Agentforce, Einstein Generative AI and the Einstein Trust Layer are referenced, so the underlying model and provider are not established. The agent supports meeting booking by returning a calendar link or meeting time options from the prospect owner's calendar; Salesforce does not establish that the agent itself creates the calendar event, and the "Meeting Booked" metric is not evidence of a calendar write. The Control Center reports records "rated hot by the agent" when Qualification is turned on, but persistence of a qualification rating on Salesforce records, its available states and the data informing it are not established by these pages. The Engagement Agent permission set grants Lead Read/Edit and cadence object create/edit/delete, but the only field-level write demonstrated in runtime documentation is Lead.HasOptedOutOfEmail set to True; broader CRM modification is not established. Review time limit is 14 calendar days, after which the agent cancels the email. Provider daily email limits are documented as up to 1800 emails a day with a Gmail account and up to 9800 with a Microsoft Exchange account; these are provider limits, not governance controls. Send as Seller includes an AI disclosure at the beginning of each generated email, which can be removed by editing the agent actions, and the disclosure is omitted when Require Manual Approval is on. Email security systems can block inbound replies from being logged. Whether the Engagement Agent user record remains the Salesforce runtime principal for all actions while Send as Seller is enabled is not stated explicitly. Lead generation, prospect discovery, sales coaching, quoting and other Agentforce Sales functionality are outside this record.

Evidence