Loading
Feature Disruption - Service Cloud VoiceRead More
Feature degradation | Gmail Email delivery failureRead More
AI Sales Agents
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Considerations for Using Agentforce Lead Nurturing

          Considerations for Using Agentforce Lead Nurturing

          Keep in mind some considerations when using Agentforce Lead Nurturing.

          Required Editions

          Available in: Lightning Experience in Enterprise, Performance, and Unlimited editions with Sales and Einstein for Sales.
          Note
          Note The Agentforce SDR name has changed to Agentforce Lead Nurturing. The new name better describes the work that the agent does to nurture existing prospects and differentiates it from the Agentforce Lead Generation agent template.

          Agent Configuration and Deployment

          • Deploying Lead Nurturing agents or agent changes via change sets or metadata is not supported and can cause the newly deployed or updated agent to stop working correctly. All agents should be created or updated in Setup or Agentforce Builder.

          Lead Nurturing Consumption of Conversations

          A Conversation is consumed when a Lead Nurturing agent sends out the initial email to a prospect. All subsequent activities carried out by the agent for that prospect are included in the initial Conversation. A user can cancel an outreach by selecting Cancel Outreach from an email task in the Activity Timeline. If a user later restarts Lead Nurturing for the same prospect, another Conversation is consumed.

          When the Lead Nurturing agent engages prospects, it consumes units of Conversations. You can track your Conversation usage in your Salesforce Digital Wallet. Each Conversation consumes Einstein Requests when it accesses the LLM.

          When you configure your Lead Nurturing agent, you choose how and when the agent engages prospects. You also select what information the agent can access to personalize outreach and replies to prospects. As the agent begins working on a prospect, it uses these settings to know how many times to reach out and how many times to reply.

          When your business purchases Conversations, Salesforce allocates a number of Einstein Requests per Conversation to your order. This allocation approximates the typical consumption pattern of Lead Nurturing agent outreach to a prospect using the default agent settings, including nudges and replies.

          Email Considerations

          • To adhere to email provider daily limits, each Lead Nurturing agent can send up to 1800 emails a day with a Gmail account and 9800 emails a day with a Microsoft Exchange account. When the agent hits the limit, it stops sending emails for the day. Keep this limit in mind when configuring your Lead Nurturing agent Engagement Rules in Setup or Agentforce Builder. If the email account assigned to the Lead Nurturing agent is also used for sending emails manually, or by another app, there's greater risk of exceeding email provider limits.
          • It isn’t possible to prioritize specific Lead Nurturing agent emails. For example, you can’t tell the agent to prioritize email replies over nudges.
          • The email account connected to Lead Nurturing can't be connected to any other user.
          • The email account connected to Lead Nurturing in Agentforce Builder must be the same email address that’s listed in the Email field of the Lead Nurturing agent user record. If not, nudge and reply emails can fail.
          • If Send as Seller is on for the agent, the record owners of prospects assigned to the agent must have email addresses correctly configured and connected to both Inbox and Einstein Activity Capture permission. If they don’t, agent emails can fail.
          • When Send as Seller is on, the agent includes an AI disclosure at the beginning of each generated email. This disclosure ensures regulatory compliance. Regulations in your area may differ. You can instruct the agent to omit the disclosure by removing the related instruction from the agent actions by using Agentforce Builder.
          • If Require Manual Approval is turned on for the agent, generated emails omit the AI disclosure because there is a sales rep reviewing each email.
          • In Einstein Activity Capture setup, the Header-only Email Capture setting within Sync Email as Salesforce Activity affects how the agent generates its emails. When Header-only Email Capture is on, the agent can’t use the email subject or body to understand prospect intent or personalize its responses. Leaving the setting off allows the agent to use the full content of the emails to provide appropriate and accurate responses. If you turn on Agentforce Lead Nurturing before you set up Sync Email as Salesforce Activity, you can’t select Header-only Email Capture.
          • If a prospect’s email address has the same domain name as the Lead Nurturing agent user record's email address, EAC considers the prospect an internal user. EAC doesn't allow the Lead Nurturing agent to send any email replies to the prospect.
          • To edit or reschedule Lead Nurturing emails, a user must connect their email account from within their user profile. If the user adds the agent's email address to their profile, an error occurs.

          Meeting Scheduling and Ownership

          • The agent can assign meetings only to Inbox users with a connected email account in their personal settings.
          • If a user isn’t listed as an option during setup, they don’t have Inbox set up or a connected email account.
          • If a group isn’t listed as an option during setup, the group doesn’t have at least one Inbox user with a connected email account or it exceeds 15 users.
          • When a group is selected as the meeting owner, the agent shows the combined availability of all Inbox users with a connected email account in that group to the customer. The agent then randomly assigns the meeting to one of the available group members.
          • For group scheduling to work, give Salesforce permission to view your free/busy time on your Gmail and Outlook calendar.
          • When Send as Sellers is enabled, meetings can only be assigned to users, not groups.

          Other Considerations

          • When Require Manual Approval is on, the record owner has 14 calendar days to approve each email. After 14 days without approval, the agent cancels the email.
          • By default, you can add up to 20 sales agents. If you need more, contact your Salesforce account executive.
          • When you add a prospect to a Lead Nurturing agent, it begins working the prospect immediately. The agent schedules the first email to be sent within an hour. The scheduled email appears in the prospect’s Activity Timeline, where a sales rep can reschedule it if needed. After the agent sends first email, it schedules the follow-up nudge email, which is visible in the Activity Timeline. If the prospect replies to any email, the agent replaces the nudge email with a drafted response and schedules the response to send within one working hour.
          • The Owner field on leads, person accounts, and contacts must be filled before assigning a record to the Lead Nurturing agent. For contacts, fill the owner field on the related account.
          • If Activity 360 Reporting is turned on, Agentforce Lead Nurturing doesn’t work
           
          Loading
          Salesforce Help | Article