# Deflect Escalation Intents

The **Deflect Escalation Intents** configurations control how Aisera handles requests that would otherwise create a ticket or connect a user to a live agent. These are tenant-level settings found in **Settings > Configuration > Deflect Escalation Intents**.

## Ticket creation deflection

### Deflect Create Ticket Request

| **Type**    | Checkbox |
| ----------- | -------- |
| **Default** | Disabled |

When enabled, Aisera intercepts requests that match an intent listed in **Escalation Intent Names** and runs a two-step clarification before allowing the ticket to be created. First, Aisera asks the user to describe their issue in more detail. If a `DeflectEscalationIntent` skill is active, that skill's form is used; otherwise, the default prompt is shown. The user's response then re-enters the full NLU pipeline — if a self-service match is found, it is served instead of creating a ticket. If no match is found, the original intent executes as normal.

Enable this when users frequently trigger ticket creation by habit rather than need, and self-service alternatives are available to catch the re-classified request.

{% hint style="info" %}
Post-conversation feedback prompts are suppressed for any conversation where deflection was attempted, regardless of outcome. 
{% endhint %}

See also: [Escalation Intent Names](#escalation-intent-names)

### Escalation Intent Names

| **Type**    | Text field          |
| ----------- | ------------------- |
| **Default** | `["Create Ticket"]` |

Defines which intents are treated as escalation intents. When **Deflect Create Ticket Request** is enabled, only intents listed here are subject to the deflection flow. When the flag is disabled, intents in this list still have two effects: the post-conversation feedback prompt is suppressed, and the conversation resolution status is set to Assisted.

Update this list when you want deflection and feedback suppression to apply to intents other than, or in addition to, `Create Ticket`.

The value must be a valid JSON array of intent system names, which are case-insensitive:

```json
["Create Ticket", "Submit Request"]
```

{% hint style="warning" %}
If the value is malformed JSON, Aisera falls back to an empty list and all escalation intent behaviors are disabled until the value is corrected. Intent system names must be used here, not display names. 
{% endhint %}

Deflect Initial Live Agent Request is not affected by this list.

See also: [Deflect Create Ticket Request](/aisera-platform/tenant-setup/aisera-platform-configuration/tenant-configuration-settings/deflect-escalation-intents.md)

## Live agent deflection

### Deflect Initial Live Agent Request

| **Type**    | Checkbox |
| ----------- | -------- |
| **Default** | Enabled  |

When enabled, Aisera pauses a user-initiated live agent request and asks a one-turn clarifying question before completing the handoff. The user's response is not re-classified — it becomes part of the conversation history passed to the agent. Disabling this setting connects users to a live agent immediately without the clarifying prompt.

Keep this enabled when you want agents to receive more context before accepting a conversation. Disable it when your users prefer an immediate connection, or when agent routing is already handled through a flow that collects context.

{% hint style="info" %}
This prompt only fires when a live agent request is triggered by a user's message. Handoffs initiated from a flow are unaffected. If the clarifying question from **Deflect Create Ticket Request** was already shown in the same conversation, this prompt is skipped automatically. 
{% endhint %}

The clarifying prompt is customizable via the `live_agent_pre_fulfillment_msg` message in Conversation Messages. See [Conversation Messages](/aiseragpt/how-to-set-up-an-aiseragpt-bot/view-conversation-messages.md) for instructions on editing this message.

### Escalation Flow Names

| **Type**    | Text field |
| ----------- | ---------- |
| **Default** | `[]`       |

No description available.


---

# 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.aisera.com/aisera-platform/tenant-setup/aisera-platform-configuration/tenant-configuration-settings/deflect-escalation-intents.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.