You are here:
Considerations for Automatic Contact Creation
Learn about requirements, email filters, and other considerations for Automatic Contact Creation.
Required Editions
| Available in: Lightning Experience |
| Available with Agentforce 1 Sales Edition |
| Available in Starter and Professional Editions |
| Available with Einstein 1 Sales Edition |
| Available with the Einstein for Sales add-on |
| Available with Sales Cloud Einstein, which is available in Performance and Unlimited Editions and for an extra cost in Enterprise Edition |
| Available with Sales Engagement in Sales, which is included in Performance and Unlimited Editions and available for an extra cost in Professional and Enterprise Editions. Sales Engagement is also available for an extra cost in Service and Lightning Platform. |
| Available with Revenue Intelligence, which is available for an extra cost in Enterprise and Unlimited Editions |
Requirements
Limitations
- No standard list views or reports show automatically created contacts.
- Automatic Contact Enhancements doesn’t update contacts added by Automatic Contact Creation unless they’re in a Buyer Relationship Map.
- Salesforce makes the best attempt to accurately associate the contact with the right
account. While we can’t guarantee it’s always accurate, these rules promote correct associations.
- Salesforce checks whether any account has contacts with the same email domain as the new contact. The account that has the most contacts with the same email domain as the new contact is selected.
- If the first rule doesn’t associate an account with the new contact, Salesforce selects the account with the most related contacts from the group of contacts. Related contacts are identified from emails and events. Each email and event includes a group of other contacts.
- If no matching account record can be determined, the contact isn’t created.
Note Auto Contact Creation considers contacts that the users own for matching. Users must own at least one contact related to the account.
Filtered Emails
Information from emails likely sent by bots or from unmonitored email accounts isn’t used to detect potential contacts. For example, Automatic Contact Creation ignores emails with sender addresses containing “no-reply” or “@group.calendar.google.com.”
New Contact Field
After Automatic Contact Creation is enabled, the ContactSource field on the Contact object
is available. After a contact is created automatically, the field is set to Auto
Create.
Automatic Retry Behavior
Sometimes, the automatic process can’t create a contact record. For example, a record isn’t created when no matching account exists. If a contact record isn’t created, the process waits at least 24 hours before running again for that potential contact. 24 hours after the first attempt, the automatic creation process runs again when a newly captured email or event includes that potential contact.
When an automatically created contact record gets deleted, there’s no retry until 30 days after the original record creation date.
Migration Behavior for Threshold Settings
If you set up Einstein Activity Capture before Spring ’26 and migrate to Sync Email as Salesforce Activity, the existing Automatic Contact Creation threshold value is used for both the new email and event threshold settings. If you set up Einstein Activity Capture in Spring ’26 or later, the default threshold for both emails and events is 3.
