> ## Documentation Index
> Fetch the complete documentation index at: https://koreai-content-gov.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Amend Entities

<Badge icon="arrow-left" color="gray">[Back to NLP Topics](/ai-for-service/automation/natural-language/nlp-topics)</Badge>

Amend Entity lets users change entity values during task execution. Example: a user books a flight and then changes the destination or travel date mid-conversation.

<Note>
  Amend Entity is supported only for English dialog task conversations. Scope: entity value replacement only (not partial modifications, deletions, or additions).
</Note>

***

## How It Works

1. **Amend Identification** — The platform's built-in NLP detects the user's intent to amend.
2. **Amending Entities** — Three flows based on utterance:
   * User refers to **entity name**: prompted for new value. (If entity appears multiple times, the most recently populated one is amended.)
   * User provides **entity value**: entity is updated. (If value matches multiple entities, user selects which to amend.)
   * User refers to **both entity name and value**: entity is updated directly.
3. **Post-Amendment Behavior** — Three options:
   * Re-execute dialog from the amended node (evaluating its connections).
   * Resume from the node where the amend was identified.
   * Resume from a specified node.

***

## Configuration

Amend behavior is set at two levels. Task-level settings override app-level.

### App Level

1. Go to **Natural Language > NLU Config > Amend Entity**.

2. Enable **Allow amend entities**.

3. Select a **Dialog Resumption** option:

   | Option | Description |
   | - | - |
   | **Re-execute from amended entity** | Resume by evaluating the amended entity's connections. Optionally clear downstream entity values and/or skip previously displayed messages. |
   | **Resume from amend identification node** | Resume from the node where the amend was triggered. |

4. (Optional) Enable **Amend Hidden Entities** to allow amendment of entities marked as Hidden.

### Task Level

1. Go to **Conversation Skills > Dialog Tasks** → open the task.
2. Click **⋯ (More Options) > Manage Amend Behavior**.
3. Select **Customize for this task**:

   | Option | Description |
   | - | - |
   | **Don't allow amend entities** | Disables amend for this task. |
   | **Re-execute from amended entity** | Same as app-level; also has downstream clear and skip options. |
   | **Resume from amend identification node** | Resume from where the amend was triggered. |
   | **Jump to a specific node** | Routes to a chosen node for custom behavior. Context contains amended entity details (previous and current values). |

   (Optional) Enable **Amend Hidden Entities** at the task level.

***

## Amend Trigger Patterns

The platform recognizes these utterance patterns as amend requests. `~amend_synonyms` includes: amend, change, modify, alter, update, replace, make, move, upgrade, want.

| Pattern | Example |
| - | - |
| `~amend_synonyms <entity> from <old> to <new>` | "change the departure date from today to tomorrow" |
| `~amend_synonyms <entity> to <new> instead of <old>` | "modify departure date to tomorrow instead of today" |
| `~amend_synonyms <entity> <old> to <new>` | "replace departure date with tomorrow" |
| `~amend_synonyms <entity> from <old>` | "alter departure date from today" |
| `~amend_synonyms <entity> to <new>` | "modify departure date to tomorrow" |
| `~amend_synonyms from <old> to <new>` | "change from today to tomorrow" |
| `~amend_synonyms to <new> instead of <old>` | "change to tomorrow instead of today" |
| `~amend_synonyms to <new> instead` | "change to tomorrow instead" |
| `~amend_synonyms it to <new>` | "change it from today to tomorrow" |
| `~amend_synonyms <entity>` | "amend departure date" |
| `~amend_synonyms <old>` | "change today" |
| `to <new> instead of <old>` | "to tomorrow instead of today" |

<Note>
  Multiple entity values can be amended in a single utterance. Example: "Change the departure date from today to tomorrow and departure city to Chicago."
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.