---
title: Defining automatic decisions in processes
related:
  - https://docs.kentico.com/k12sp/on-line-marketing-features/managing-your-on-line-marketing-features/marketing-automation/working-with-the-automation-process-designer/defining-user-choice-steps-in-automation-processes.md
  - https://docs.kentico.com/k12sp/macro-expressions/writing-macro-conditions/building-conditions-using-macro-rules.md
  - https://docs.kentico.com/k12sp/on-line-marketing-features/configuring-and-customizing-your-on-line-marketing-features/on-line-marketing-macros.md
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

> **Info:** **Kentico EMS required**
>
> Features described on this page require the **Kentico EMS** license.

[Marketing automation](https://docs.kentico.com/k12sp/on-line-marketing-features/managing-your-on-line-marketing-features/marketing-automation.md) allows you to split processes into multiple branches. You can define conditional steps, which automatically determine how contacts continue through the process.

The system evaluates automatic decision steps based on dynamic conditions. For example, you can create conditions that check the values of the given contact's attributes, or their previous activity on a website.

## Adding basic conditions

Condition steps split the process into two branches – one if the condition is true, the other when false. The step automatically moves contacts forward to the next step based on the result of the condition.

To add a condition step:

1. [Place](https://docs.kentico.com/k12sp/on-line-marketing-features/managing-your-on-line-marketing-features/marketing-automation/working-with-the-automation-process-designer/managing-automation-process-steps.md) the **Condition** step onto the grid from the designer toolbar.
2. Edit the step by clicking the pencil icon next to its name or by double-clicking the step box.
   - The **Process step properties** dialog opens.
3. **Edit** the [condition](https://docs.kentico.com/k12sp/macro-expressions/writing-macro-conditions/building-conditions-using-macro-rules.md) in the **Condition** field.

   - If you write the macro condition manually, your expression must return either _true_ or _false_.
4. (Optional) Type a text description of the condition into the **Designer label** field.
5. Click **Save** and close the dialog.
6. Integrate the condition into the flow of the process by [connecting](https://docs.kentico.com/k12sp/on-line-marketing-features/managing-your-on-line-marketing-features/marketing-automation/working-with-the-automation-process-designer/connecting-automation-process-steps.md) a preceding step.
7. Connect both source points of the condition to other steps in the process.

For example, the process shown below uses a condition to send a campaign email only to contacts who fulfill a specific condition (have submitted a certain form). If the contact in the process does not meet the condition, the process moves directly to the **Finished** step.

![Condition step that moves the process to the Send newsletter issue step if true](https://docs.kentico.com/docsassets/k12sp/defining-automatic-decisions-in-processes/condition_step.png "Condition step that moves the process to the Send newsletter issue step if true")

## Adding Multi-choice steps

Multi-choice steps can split the process into any number of branches. You need to define a set of _cases_ for the step, each with its own condition. When a contact reaches the step in the process, the system automatically evaluates the conditions of the cases:

- If the condition is fulfilled for exactly one case, the process automatically moves the contact to the step connected to the corresponding source point.
- If multiple conditions are fulfilled, designated users need to [manually choose](https://docs.kentico.com/k12sp/on-line-marketing-features/managing-your-on-line-marketing-features/marketing-automation/managing-the-flow-of-contacts-in-automation-processes.md) the next step for the given contact.
- If none of the conditions are fulfilled, the process continues through the _else_ branch.

To add Multi-choice steps to your process:

1. [Place](https://docs.kentico.com/k12sp/on-line-marketing-features/managing-your-on-line-marketing-features/marketing-automation/working-with-the-automation-process-designer/managing-automation-process-steps.md) the **Multi-choice** step onto the grid from the designer toolbar.
2. Integrate the step into the flow of the process by [connecting](https://docs.kentico.com/k12sp/on-line-marketing-features/managing-your-on-line-marketing-features/marketing-automation/working-with-the-automation-process-designer/connecting-automation-process-steps.md) a preceding step.
3. [Define cases](#defining-cases-for-decision-steps-with-multiple-branches) for the step.
4. Connect the _else_ source point (red) to another step.
5. Connect the source points of all cases to other steps.

## Adding First win steps

First win steps can split the process into any number of branches. You need to define a set of _cases_ for the step, each with its own condition. When a contact reaches the step in the process, the system evaluates the cases according to their order. If the step finds a matching condition, the contact moves forward to the step connected to the corresponding case (the remaining cases are not evaluated). If none of the conditions are fulfilled, the process continues through the _else_ branch.

To add First win steps to your process:

1. [Place](https://docs.kentico.com/k12sp/on-line-marketing-features/managing-your-on-line-marketing-features/marketing-automation/working-with-the-automation-process-designer/managing-automation-process-steps.md) the **First win** step onto the grid from the designer toolbar.
2. Integrate the step into the flow of the process by [connecting](https://docs.kentico.com/k12sp/on-line-marketing-features/managing-your-on-line-marketing-features/marketing-automation/working-with-the-automation-process-designer/connecting-automation-process-steps.md) a preceding step.
3. [Define cases](#defining-cases-for-decision-steps-with-multiple-branches) for the step.
4. Connect the _else_ source point (red) to another step.
5. Connect the source points of all cases to other steps.

## Defining cases for decision steps with multiple branches

Cases represent individual branches of _Multi-choice_ and _First win_ steps. To set up cases for a step:

1. Click **Add new case** () to create the required number of branches.
2. Click **Edit case properties** (pencil icon) for each case.
   - The **Process step properties** dialog opens.
3. Specify the case's [condition](https://docs.kentico.com/k12sp/macro-expressions/writing-macro-conditions/building-conditions-using-macro-rules.md) in the **Condition** field.
4. (Optional) Fill in the **User action text** and **User action tooltip** for the case.

   - Users can see these text values when [manually managing](https://docs.kentico.com/k12sp/on-line-marketing-features/managing-your-on-line-marketing-features/marketing-automation/managing-the-flow-of-contacts-in-automation-processes.md) the flow of the process for contacts in the given step.
5. Open the **Security** tab and choose which users or roles are [allowed](https://docs.kentico.com/k12sp/on-line-marketing-features/managing-your-on-line-marketing-features/marketing-automation/working-with-the-automation-process-designer/configuring-step-security-for-automation-processes.md) to manually move contacts through the given case.

   - By default, cases inherit the security settings of the step.
6. Click **Save** and close the **Process step properties** dialog.

You can see the cases listed inside the step. Each case provides a separate source point for connecting the decision step to the appropriate branch of the process.