Cleaning action

Cleaning actions

When actioning Kernel's recommendations, the primary field to use is called Cleaning action, which is equal to one of 5 values.

Action	How to understand it	Default max risk tier
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.	Medium
Merge	The account has a duplicate, is not the primary record, is part of a valid duplicate group (more than one record), and has no regional exceptions or is a standalone child.	Medium
Associate	Account has an identified parent in the CRM	None
Associate (missing parent)	Account has an identified parent that is not in the CRM	None
Review	Flags records for manual review if Kernel has detected low confidence in its analysis

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, additional Data helps provides context around the action.

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 master 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.