Kick-off
What you can expect from the kick-off with your dedicated Kernel Solutions Engineer.
Prerequisites
In order to start the Kernel integration, we must have:
CRM access
Basic configuration
Kick off call
The kickoff call is the formal start of the Kernel implementation. This is when we will introduce you to the team that will be working with you for the duration of the implementation. This includes a solutions engineer and a customer success manager.
In the initial call, we will:
Define what success means for you in the implementation
Ensure alignment on deployment timelines and scope
Ensure Kernel is correctly integrated to your CRM
Onboard you to the Kernel platform, ensuring all required users are granted access
Your dedicated Solutions Engineer will work with you to confirm you have all of the knowledge needed to be able to configure Kernel to your use case, allowing independence to configure logic outside of your regular sessions.
In further sessions, they will also guide you through interpreting the data on your accounts, as well as taking mass actions.
Kernel App
Our app allows for all the configuration you need to successfully clean and enrich your CRM. This includes the custom configuration, testing, and tooling you need to confidently trust the data and perform mass actions on your CRM accounts.
You will get access to the app as part of the implementation and have a dedicated Solutions Engineer available to provide support when configuring your business logic.
Custom Configuration
ConfigurationKernel is configurable to your custom use case.
This involves looking at fields on any object within your CRM to help inform our cleaning actions, rules, and risk scoring. In order for this to be most effective and for us to proceed quickly, it is useful for you to start considering the types of data points that are in your CRM, which can be useful in determining:
Risk Scoring
Kernel judges the risk of accounts. This is asking "what is the risk of performing a destructive mass action on this account?" To do this, we look at a variety of fields. We include standard fields such as opportunity counts, contacts count and recent activity. We also look at custom fields within your CRM that can be used to give us better insight into how you look at these accounts.
To best configure Kernel it's good for you to consider the following questions:
What defines a customer?
What factors determine an account to be good vs. bad?
Do you care about open opportunities?
Are tasks indicative of recent activity on an account?
Do you have integration users or queue users that own many accounts?
Are all of your owners active users or do inactive users own accounts that you want to keep?
Safeguarding
Kernel offers safeguards which prevent any mass actions taking place. This is determined by looking at fields within your CRM. If these fields or conditions are met then Kernel will not perform any mass actions.
You have full control in which fields are used to set the safeguards and which accounts are therefore protected.
Risk Tiers
Kernel uses risk tiers to batch actions so that you can effectively work on subsets of accounts within your CRM. This means that you can perform different types of actions across different risk tiers of accounts so that we work through your CRM methodically.
For example you can start with performing all associations on very low-risk accounts as this is a non-destructive action on the low-risk accounts. You could then move to higher-risk accounts or a more destructive action such as a merge or a deletion. This then allows us to segment the riskiest of actions such as merging high-risk accounts so that they can be dealt with in a different way.
You have full control over determining these risk tier and also filtering all of our mass action capabilities by risk tier so that you can be comfortable in all the actions that you are undertaking.
User Types
Account ownership is an integral part of how Kernel thinks of Account risk. Kernel's customizable algorithm detects which accounts are owned by active sales reps.
Kernel allows you to add custom definitions of active/inactive users. These can all be configured in the app.
Active usersOnce the CRM is connected and you're onboarded onto the app, you'll be able to see all of the configurable options.
Last updated