Overview
Cleaning actions
When actioning Kernel's recommendations, the primary field to use is called Cleaning action, which is equal to one of the following values:
Delete
The account is out of business or the website is not working, is not an absorbed subsidiary, and is not actively owned. It is generally safe to delete.
Merge
The account has a duplicate, is not the primary record, and is part of a valid duplicate group.
Associate
The account has an identified parent in the CRM that it should be linked to.
Associate (missing parent)
The account has an identified parent that is not yet in the CRM. Kernel will create the parent and link the accounts.
All actions are configurable by the user, so the exact definition will depend on each user's individual setup.
Reasoning behind the action
Each cleaning action comes with a 1-sentence summary of why the specific action was chosen for the account.
In addition, depending on the cleaning action, Kernel shows extra context fields to explain why that action was recommended.
Kernel App
Actions are performed within the app with interfaces for each. Each interface contains all the necessary data to perform mass actions with confidence.
Actions can be filtered by risk and CRM fields added to any view. All actions can be exported as shown in the app as a CSV.

Delete
The delete action will permanently remove accounts from your CRM. The deletion rules are configurable within the app allowing for control over parameters such as website functionality, deleting generic URLs (e.g hotmail.com) or status of the company.
You can also configure rules that prevent deletion such as the account having active ownership in your CRM.

Associate
The associate action will tie accounts together in your CRM using the native hierarchy functionality. Completed accounts can be viewed with rejected accounts flagged for review by the Kernel team.

Merge
Groups of accounts to be merged are displayed together. Within this view you can add any fields from your CRM to compare. You also get full insight on all risk related items that are being used to determine the groups.
The "Compare" function allows you to see the outcome of your survivorship logic on that group. The primary record after merge will be shown with all CRM fields. Logs allow for the full history of the group showing any merges that have occurred, fields before/after and all the linked objects that have been reparented in the merge.
Recalculate
After making configuration changes, you can trigger a recalculation of merge, associate, and delete recommendations directly from the app. This rebuilds the full set of groups based on your updated logic. Note that recalculating deletes all existing groups and recreates them — this process can take a few minutes.
Safeguarded accounts
By default, safeguarded accounts do not appear in merge groups. You can enable an option in the app to allow merging of safeguarded accounts. Once enabled, they will surface within the relevant groups and can be filtered in or out.

Last updated

