# Managing actions

Kernel tooling is built to enable you to take mass actions and not check every record. We utilise our cleaning actions along with risk tiers to segment groups of accounts that can be actioned in phases.

The result is a risk/action matrix that moves from very low risk, non-destructive actions to high risk, destructive actions.

**Non-destructive actions:** Associate, Associate (missing parent). These actions keep the account in tact and can be easily reversed.

**Destructive actions:** Merge, Delete. These actions remove accounts from your CRM and will require restoration to undo.

The best roll outs of Kernel follow a phased approach as shown on the diagram below. We move from green to red, allowing you to manage the changes with your team as we proceed.

<figure><img src="/files/cDPcMJSgBhGYGAtNyZDy" alt=""><figcaption></figcaption></figure>

Green phases can be actioned in mass groups with little human review. These are non-destructive, reversible actions and/or accounts with little to no risk, as defined by your custom rules. We typically see large improvements made very quickly here across our customers.

Yellow phases begin to deal with more important accounts that are in use by reps and likely to have changes noticed. Non-destructive actions can still be reversed but could impact reporting or rep activity.

Red phases are destructive actions on the most important accounts in the CRM. These accounts should have more time spent reviewing before taking mass actions. Understanding on the wider CRM is important here and proper rep management as this will affect current books.

Purple phases are safeguarded and review accounts. These will be reviewed manually and protected from actions entirely.

Kernel does have the ability to rollback destructive actions if needed along with the reparenting of objects to the previous account.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kernel.ai/managing-actions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.