> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.goautonomous.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Using Autonomous Mode

> A full walkthrough of the Autonomous Mode page — creating, configuring, and duplicating automation rules.

## The Autonomous Mode page

Navigate to **Administration > Company Settings > Automation** to reach the Autonomous Mode landing page.

The page displays all existing automation configurations in a table showing the **Name**, **Intent**, **Mode**, **Source**, **Source Value**, **Trigger**, and **Certainty** for each rule.

* To **create a new rule**, press **"Add automation"**.
* To **edit an existing rule**, click anywhere on the relevant row to open the configuration pane.

## Configuring an automation

When creating or editing a configuration, you'll see the following fields:

### Name

Enter a unique name for your automation configuration.

### Intent

Select the intent you want to automate. You can only automate intents that have been configured with fields in your Company Settings.

### Mode

Choose how the automation is applied to requests.

<Tabs>
  <Tab title="Complete Cart">
    Automates the entire request on an "all or nothing" basis. **All fields** in both the summary and the product cart must be validated for the order to be automated.

    **Example:** If an order has 50 products and just one is missing a quantity, the entire order is flagged for manual review.
  </Tab>

  <Tab title="Line Item">
    Automates only the specific lines within an order that meet your criteria, leaving the rest for manual review (all Summary fields must still be validated).

    **Example:** If an order has 50 products and one is missing a quantity, the 49 validated products are automated while only the single incomplete line requires human review.
  </Tab>
</Tabs>

### Source and Source Value

Select the inboxes or areas you want to automate.

<Note>
  To avoid conflicts: you cannot select a specific inbox if its area is already used in another rule, and you cannot select an area if an inbox within it is already part of another rule.
</Note>

### Senders

Create a sender list to include or exclude specific emails, domains, or accounts from this automation.

| Field      | Description                                                                                                                                                        |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Mode**   | Choose **Include** to only automate requests from senders on your list, or **Exclude** to automate everyone except those on the list.                              |
| **Source** | Specify whether your list contains **emails** or **accounts**.                                                                                                     |
| **Upload** | Provide your list as a CSV file with all entries in a single column. For email lists, you can mix full addresses and entire domains (formatted as `@example.com`). |

### Certainty

Set the minimum confidence score (0–100%) the AI must have in the identified intent for a request to be automated.

<Tip>
  We recommend starting with a threshold of **90%**.
</Tip>

### Automation Prevention

Decide whether errors or warnings on a request should block it from being automated.

<Note>
  This feature may not be available for all customers. Contact your Customer Success representative to enable it.
</Note>

### Conditions

Set specific conditions based on product cart fields to determine whether a request is eligible for automation. For example, you could require that an order total is below \$100,000.

The available conditions change depending on the **Mode** you selected — see the section below.

***

## A deep dive into conditions

Conditions let you define precise rules for automation eligibility. Their behaviour differs depending on whether you're using Complete Cart or Line Item mode.

### Complete Cart mode

You can set **one condition** that applies to the order as a whole.

* **Logic:** The condition is based on the sum of a numerical field in the product cart. Available operators: `=`, `>`, `<`, `!=`.
* **Example:** Only automate orders where the sum of the unit price is less than €2,000.

### Line Item mode

You can set **up to two conditions** that apply to each individual line.

* **Logic:** Conditions apply to specific fields of each line item and can be joined by an **AND/OR** operator.
  * For non-numeric fields (e.g. product colour): `=` or `!=`
  * For numeric fields (e.g. quantity): `=`, `>`, `<`, `!=`
* **Example:** Only automate lines where the product colour is blue.

***

## Duplicating configurations

To save time when setting up a new rule that's similar to an existing one:

<Steps>
  <Step title="Select the configuration">
    Tick the checkbox next to the configuration you want to duplicate.
  </Step>

  <Step title="Press Duplicate">
    Click the **Duplicate** button in the toolbar next to the search bar.
  </Step>

  <Step title="Update the values">
    The configuration pane will open with the duplicated values. Update any fields as needed.
  </Step>

  <Step title="Save">
    Press **Save** to create the new configuration.
  </Step>
</Steps>