Kernel fields

Kernel's AI Cleaning & Hierarchies module comes with 23 custom fields.

No fields are required to use Kernel however we recommend introducing Kernel data to your CRM to allow for reporting and improved rep outcomes. During implementation we will work with you to ensure you have all the fields you need to use/action the data.

Fields

Kernel provides many custom fields that give direct recommendations, insights, or explanations behind the cleaning recommendations and enrichment fields. Depending on the scope of work, field sets may or may not be required to be configured within your CRM. The full list of fields can be seen below:

Feedback

Kernel's feedback field is a required field to be configured within the CRM as part of the implementation process. This allows users to directly submit feedback on the account or object, which will be ingested by our support team to promptly act upon.

Cleaning module

The cleaning of accounts does not require any fields to be created within your CRM, as the majority of work is carried out via through the Kernel Platform. However, to have data pushed up to your CRM (if via inbound), fields would need to be created.

Foundational enrichment

The below sheet details the recommended fields to be configured within your CRM to allow the full range of foundational enrichment to be pushed onto accounts.

Agentic firmographics

The below fields are used for AI-powered firmographic data including HQ, Headcount, and Revenue. See Agentic firmographics for details on how these values are determined.

Should you have any bespoke data points outside of those listed, your Solutions Engineer will guide you to ensure the correct configuration is setup.

Standard vs. custom fields

While Kernel can write to both standard and custom Salesforce fields, we strongly recommend a safer approach to prevent accidental data overwrites.

The best practice is to have Kernel write its findings to a dedicated, read-only custom field. This isolates Kernel's data, allowing you to use Salesforce logic to control how the primary field is populated. As shown in the example, this gives your team the ability to create manual overrides that always take precedence, ensuring you have final say over your data.