Find out when your prospecting agent creates records, which fields it populates, and how it avoids creating duplicate records.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with the Agentforce for Sales or Agentforce for an Industry add-on, or in Agentforce 1 Sales and Industry Editions where included. Requires each user to have the Agentforce for Sales or Agentforce for an Industry add-on to access actions. |
When the Agent Creates Records
The agent creates a record when it finds a qualified prospect from a connected data vendor who isn't already in your CRM.
Which Records the Agent Creates
The record type set in your agent's configuration determines which type of record the agent creates for prospects who aren't in your CRM yet. By default, the agent creates contacts.
| Record Type | What the Agent Creates |
|---|---|
| Lead | One lead record for each qualified prospect. |
| Contact | One contact record for each qualified prospect, linked to an account in your CRM. |
Which Fields the Agent Populates
The fields that the agent populates depend on the type of record that it creates. The table shows which fields the agent populates for each record type.
The field mapping is fixed, and you can't change it. The agent populates only the fields in the table and doesn't populate any other standard or custom fields. Fields such as Lead Source and Lead Status get your org's default values, if you set any. The agent doesn't include data vendor fields, such as department, seniority, or location.
| Field Name | Record Type | Value Entered |
|---|---|---|
| First Name | Lead and Contact | The prospect's first name |
| Last Name | Lead and Contact | The prospect's last name |
| Title | Lead and Contact | The prospect's job title |
| Company | Lead | The prospect's company name |
| Account | Contact | The account the prospect was found in. |
| Lead and Contact | The prospect's business email address | |
| Phone | Lead and Contact | The prospect's main business phone number |
| Owner | Lead and Contact | The sales rep assigned to the prospect |
The agent creates records on behalf of the sales rep, so the rep's object and field permissions apply. Make sure that sales reps can create the records and edit the fields that the agent populates. If the sales rep can't edit a field, the agent leaves the field blank.
Your org's rules also apply. Validation rules and automation such as flows and triggers run for records that the agent creates, just as they do for records that the user creates. The agent can create many records in one run, so check the lead and contact flows and triggers that run when a record is created.
- If your lead or contact records require fields that the agent doesn't populate, or if a validation rule depends on fields that the agent doesn't populate, record creation fails for those prospects.
- The agent skips creating records for prospects without an email address.
How the Agent Avoids Duplicate Records
Before the agent creates a record, it looks for an existing record of the same type that matches the prospect's name, title, company or account, email address, and phone number. If the agent finds an exact match, it uses that existing record and doesn't create one. If any of those fields differ, the agent creates a new record. The agent checks only records that the sales rep can see. If a matching record exists but the rep can't see it, the agent creates a duplicate record.