You are here:
Considerations for Candidate Sourcing with Agentforce
Learn about some key factors that affect the Recruiter agent’s performance in candidate sourcing.
Required Editions
| View supported product editions. |
Note The agent helps recruiters efficiently build a pipeline of qualified candidates.
Recruiters remain responsible for identifying the best candidates for a role.
- The Email Candidate Leads flow uses the Send Email flow action to send outreach emails to candidates. Each licensed org can send single emails to a maximum of 5,000 external email addresses, or recipients, per day. A day is based on Greenwich Mean Time (GMT). After you’ve sent 5,000 external emails in a day, the agent can’t send the outreach emails to candidates until the next day. See Flow Core Action: Send Email.
- The Create Candidate Leads flow generates leads using the format: <Recruitment posting> <Firstname> <Lastname>. To change this format, customize the flow.
- If the Create Candidate Leads flow finds more than 20000 leads, it creates them asynchronously. The recruiter receives an email after all the leads are created.
- If a recruiter clicks Send Email before the lead creation job finishes, Salesforce creates all the leads, but sends emails only to the leads created so far.ß
- When using the Candidate Sourcing subagent:
- The Standard Lead Duplicate Rule prevents the Create Candidate Leads flow from
creating more than one lead record with the same email address. As a result, a
qualified applicant from the past can be treated as a potential candidate for the role
advertised in only one recruitment posting at a time. To remove this limitation, make
one of these changes to the duplicate rule.
- Edit the Standard Lead Duplicate Rule and turn off the Alert operation on create.
- Deactivate the duplicate rule after you verify that turning off the check doesn’t affect any of your workflows.
- Create a custom rule that matches the First Name, Last Name, Email, and Title field values to identify a duplicate lead record.
- Recruiters can ask the agent to get application forms that are relevant to the role
in a recruitment posting, and from a particular stage in the recruitment process. By
default, the Candidate Sourcing subagent instructs the agent to consider these values
as valid stages for an application form.
- New
- Details Validated
- Evaluation Complete
- Vetting Complete
- Rejected
- Approved
- Offered
To use the prebuilt functionality, configure these picklist values for the Stage field on the Application Form object. If your recruitment process has a different set of stages, make sure that you customize the subagent instructions and update the list of valid stages.
See Add Picklist Values and Edit a Standard Subagent in the Legacy Builder.
- The Get Relevant Application Forms flow includes constants to limit the number of
recruitment requisitions and application forms retrieved, and the number of
application forms returned. Here are the default values of these constants.
- MaximumNumberOfRecordsToStore: limits the number of recruitment requisitions retrieved to 15.
- TotalApplicationFormsLimit: limits the number of application forms retrieved to 2000.
- RelevantApplicationFormsReturnLimit: limits the number of application forms returned by the flow to 50.
- The Standard Lead Duplicate Rule prevents the Create Candidate Leads flow from
creating more than one lead record with the same email address. As a result, a
qualified applicant from the past can be treated as a potential candidate for the role
advertised in only one recruitment posting at a time. To remove this limitation, make
one of these changes to the duplicate rule.
Did this article solve your issue?
Let us know so we can improve!
