Internal data requirements
Kernel uses unstructured data in your CRM to make better decisions about each account
Kernel runs its analysis and recommendations based on how a rep would see the account, which requires broader access to the account and its associated data.
Kernel's Salesforce integration comes with a recommended permission set providing view access to various objects and fields required for the best results.
Required account fields
Id
Website
Name
LastActivityDate
CreatedDate
Type
If an alternative field is used to track the customer lifecycle, please specify this.
Billing/ShippingAddress
OwnerId
In addition, Kernel will ask for the following custom fields, where available:
Legal name
Trading/DBA name
Billing email
Account notes / SDR notes
LinkedIn URL
Account status
Alternative website/domain
Required opportunity fields
Opportunity data is used in (a) the algorithm for safeguarding active accounts, (b) the algorithm for determining the primary account among a group of duplicate accounts, and (c) establishing the account’s identity by looking at the associated opportunity names.
If it's not possible to allow read access to the fields outlined below, it can be sufficient to provide access to an account-level field that rolls up the number of open opportunities associated with the account.
Id
Name
Stage
CreatedDate
CloseDate
Required contact fields (Salesforce)
Kernel uses the contact data to establish the identity of an account. Emails are converted to domains ([email protected] becomes kernel.ai), and only the related domains of an object are stored by Kernel.
Id
Required task fields
Tasks are used (a) for establishing the primary in a group of a duplicates and (b) identifying the identity of the account.
Id
Name
Subject
Description
Last updated