Alternative deployments

Kernel has a suite of tools that allow for varying deployments. We only deal with large enterprises with all tools designed for complex use across nuanced CRMs

Kernel has various deployment options:

• Supported CRMs

• Starting outside of CRM, moving to supported

• Outside of CRM with orchestration tool

• Non-supported CRM

Supported CRMs

Recommended approach

We currently support Salesforce and Microsoft Dynamics natively. Deployments within these CRMs offer the full suite of Kernel tooling and functionality. We use native APIs for efficiency and the best integration experience.

Salesforce integrationDynamics integration

Outside of CRM to supported CRM

Kernel can provide data in flat files if the initial integration with a supported CRM is delayed. This process involves CSV transfers of data. This method limits the capabilities of Kernel and can also take longer to process data than when integrated with a supported CRM. We suggest this method when looking to do an accelerated cleaning process alongside a slow process to gain CRM access.

Process:

1

Share CRM via CSV

Kernel requires a full CRM export via CSV. At minimum, CRM ID, Name and Website needs to be provided. Kernel works better with more contextual data from your CRM. Fields such as object rollups (counts of opportunities), related domains (other URLs or domain of emails) and unstructured notes are all valuable. Our team will help guide through the exact fields.

2

Initial Cleaning

Kernel will process the provided data through our basic cleaning processes in the same way as any other deployment type.

3

Configuration

You won't have access to the Kernel app to make configurations on your cleaning. Kernel will provide the basic cleaning configurations available while not connected to the CRM. This will take the form of a single working session.

4

Iteration

Data samples will be shared by the Kernel team via CSV files. This will allow for the reviewing of Kernel cleaning through working sessions configure Kernel fully. This will occur over the initial 4 weeks.

5

Delivery

Kernel will deliver the full CRM of data via CSV.

6

Connection

After the initial implementation and delivery of data we will move to integrating with the CRM before the next refresh.

Kernel will not be able to perform any mass actions until connected to the CRM. Kernel will not offer refreshes of data via CSV after the initial implementation.

Outside of CRM with orchestration tool

Kernel has various APIs that we can configure to work with orchestration tooling. This requires technical set up and maintenance from your team. The minimum requirements are the ability to poll an API endpoint and work through paginated API results. Using our APIs, you will be able to configure a full data flow for inbound accounts and data refreshes.

On kick-off, Kernel requires a full CRM export via CSV. At minimum, CRM ID, Name and Website needs to be provided. Kernel works better with more contextual data from your CRM. Fields such as object rollups (counts of opportunities), related domains (other URLs or domain of emails) and unstructured notes are all valuable. Our team will help guide through the exact fields.

Inbound API

Our Inbound API offers just-in-time research of any account on your custom data points. Upon triggering the API, Kernel will research the provided entity and return data to your CRM. Our full documentation provides all the details (Inbound API). To run this API you will need to provide a CRM ID, Name and Website for the account.

Using this API your orchestration tool will then manage the flow of data from Kernel to the account in your chosen destination.

Bulk API

Our Bulk API allows for mass updating of data from the Kernel database to your orchestration tool. This operates similarly to the Salesforce Bulk API returning all accounts with your datapoints. The orchestration tool will then need to map these accounts and fields. Full documentation is provided (Bulk Retrieval API).

This API is intended for data refreshes of large amounts of accounts. When approaching a refresh Kernel will prepare the data and enable the Bulk API. You will then be given an API token that allows you to retrieve the data for 7 days. This API will return the latest data for those accounts. The running of this is handled by the Kernel team so there is no need to poll the API.

Kernel does not offer an API or tooling to handle mass actions when operating via an orchestration platform. All data will still be provided including recommended cleaning actions, identification of duplicate/parent accounts and reasoning, however, you will need to handle the actioning of that data.

Non-supported CRM

Kernel supports Salesforce and Microsoft Dynamics. Kernel does not support any other CRMs. Kernel will offer technical support on the usage of our APIs along with best practice in using orchestration platforms. We can't however offer technical support on the orchestration platforms or other CRM systems that we don't support.