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

# Automate the Helpdesk with triggers

> Automate your Helpdesk with ordered rules that run when tickets are created or updated, setting statuses, routing work, and adding notes for you.

Helpdesk triggers are automation rules for the Chatbase Helpdesk. Each trigger watches for tickets that are **created** or **updated**, checks them against the conditions you define, and runs the actions you choose, such as setting a status, assigning a team or agent, adding tags, or sending an email, a webhook or a Slack message. Triggers are set per AI agent, work on tickets from every channel, and are included on every plan with the Helpdesk (Basic plan or higher).

The mental model is simple: **WHEN** a ticket matches your conditions, **THEN** run these actions.

Triggers run **in order, top to bottom**, and **every matching trigger fires**. This lets you stack rules (one to route billing questions, another to prioritize angry customers) and they all apply to the same ticket in the order you set.

You configure triggers from **Settings → Helpdesk → Triggers**.

To act on tickets that have waited too long, where nothing creates or updates them, use [Automations](https://chatbase.co/docs/user-guides/chatbot/help-desk/automations.md).

![Triggers settings page listing existing triggers](https://mintcdn.com/chatbase/XFP5f4YsqhVtBOe3/user-guides/images/help-desk/triggers/triggers-settings.png?fit=max\&auto=format\&n=XFP5f4YsqhVtBOe3\&q=85\&s=fc88b0e0975722b2245cce1e9e555e16)

> [!NOTE]
>
> Triggers require the Helpdesk to be enabled for your AI agent. If you haven't set it up yet, see the [Helpdesk overview](https://chatbase.co/docs/user-guides/chatbot/help-desk/help-desk-overview.md).

## How a Trigger Works

Every trigger is made of four parts:

> [card] Details
>
> A **name** and optional **description** so your team knows what the rule does and why.

> [card] Conditions (WHEN)
>
> The rules that decide whether a ticket matches, based on its status, channel, assignee, team, priority, tags, custom fields, the requester's contact record, and more.

> [card] Actions (THEN)
>
> What happens when a ticket matches: set a status, assign work, add a note or tags, send an email, a webhook or a Slack message. Actions run in order.

> [card] Status
>
> Whether the trigger is **Active** or **Paused**. Only active triggers run.

### Example: escalate urgent billing tickets

This example trigger raises the priority of billing emails that mention a chargeback and alerts the team:

| Part | Setting |
| - | - |
| **Name** | Escalate chargebacks |
| **Match ALL of** | Ticket is **Created**; Channel is any of **Email** |
| **Match ANY of** | Subject contains any of `chargeback`, `dispute`; Description contains any of `chargeback`, `dispute` |
| **Actions** | Set priority **Urgent**; Add tags `billing`; Assign team **Billing**; Send email to **Assigned team** |

## How Triggers Run (Cycles)

Triggers don't just run once from top to bottom: they run in **cycles**. This lets one trigger's action feed into another trigger's conditions, so your rules can build on each other.

Here's what happens each time a ticket is created or updated:

**1. Scan from the top**

Chatbase checks every active trigger in order, top to bottom, against the ticket.

**2. Matching triggers fire**

Each trigger whose conditions match runs its actions. A trigger fires at most once per run.

**3. A change restarts the scan**

If any trigger changes the ticket (for example, it sets a new status or assigns a team), the scan **starts over from the top**. Triggers that hadn't matched before now get another chance, because they're re-checked against the ticket's updated state.

**4. Repeat until nothing changes**

The cycle keeps restarting until a full pass fires nothing new. At that point the ticket is done and the final result is saved.

Because each trigger fires at most once per run, a run can't loop forever: it has at most one more pass than you have triggers. As a hard backstop, a single run stops after 1,000 firings. Changes that triggers make to a ticket never start a new run of their own.

> [!TIP]
>
> Ordering still matters. Put the trigger that sets the foundational value (like status or team) **above** the triggers that react to it, so the reaction gets picked up when the scan restarts.

## The Default Team Trigger

When you enable the Helpdesk, Chatbase adds a trigger named **Route to default team**, described as "When a new ticket still has no team, assign it to your default team." Its conditions are **Ticket is Created** and **Team is No team**, its action assigns the **Default team**, and it sits last in the list so your own routing triggers run first.

This trigger is what sends unrouted tickets to your [default team](https://chatbase.co/docs/user-guides/chatbot/help-desk/teams.md). It's an ordinary trigger: if you pause or delete it, tickets that no other trigger routes stay without a team.

## Creating a Trigger

**1. Open Triggers**

Go to **Settings → Helpdesk → Triggers** and click **New trigger**. A panel opens from the right.

**2. Name your trigger**

Give it a clear **Name** (for example, "Route billing tickets") and an optional **Description** explaining what it does.

![New trigger panel with name, conditions, and actions](https://mintcdn.com/chatbase/XFP5f4YsqhVtBOe3/user-guides/images/help-desk/triggers/create-triggers-naming.png?fit=max\&auto=format\&n=XFP5f4YsqhVtBOe3\&q=85\&s=38b731d73e8efcc7a959e6036eda1cbb)

**3. Set the conditions (WHEN)**

Add the conditions that decide when the trigger should run. See [Conditions](#conditions) below for every available field and operator.

**4. Add the actions (THEN)**

Add at least one action to perform when a ticket matches. See [Actions](#actions) below for the full list.

**5. Activate and save**

Use the **Active / Paused** toggle to decide whether the trigger runs, then click **Create trigger**. New triggers are active by default.

## Conditions

Conditions decide which tickets a trigger applies to. They're organized into two groups:

* **Match ALL of**: every condition in this group must match.
* **Match ANY of**: at least one condition in this group must match. This group is optional and is combined with the ALL group using **AND**.

> [!TIP]
>
> Use **Match ALL of** for the rules that must always be true (for example, "Status category is New") and **Match ANY of** for a set of alternatives (for example, subject contains "refund" **or** "chargeback").

### When does a trigger run?

Add a **Ticket is Created** or **Ticket is Updated** condition to control when a trigger fires. If you don't add one, the trigger runs on **both** create and update.

Triggers run only when a ticket is written. There's no clock: nothing re-checks tickets over time, so a trigger can't fire because a ticket has waited a certain time.

| Event | Runs |
| - | - |
| A ticket created by the AI agent, by a teammate in the Helpdesk, or through the API | **Created** triggers |
| A customer reply or an agent reply on the ticket | **Updated** triggers |
| A manual change to status, assignee, team, priority or a custom field | **Updated** triggers |
| An internal note | Nothing |
| A manual [takeover](https://chatbase.co/docs/user-guides/chatbot/help-desk/takeover.md) | No **Created** triggers (so the default team trigger doesn't run), but the assignment that follows runs **Updated** triggers |

Setting a field to the value it already has changes nothing and runs no triggers.

Some replies also change the ticket on their own:

* A customer reply moves a ticket in **On customer**, **On hold** or **Closed** to the default **On you** status.
* An agent reply reopens a **Closed** ticket to the default **New** status. It never moves **On you** to **On customer**; only **Send and close** changes the status as you send.
* An agent reply to an unassigned ticket assigns the ticket to that agent.

### Ticket condition fields

| Field | What it matches | Operators |
| - | - | - |
| **Ticket** | Whether the ticket was just **Created** or **Updated**. Use this to scope when the trigger runs. | `is` |
| **Status category** | The ticket's category: **New**, **On you**, **On customer**, **On hold**, **Closed**, or **Cancelled**. | `is`, `is not`, `is any of`, `is none of`, `changed`, `not changed`, `changed to`, `not changed to`, `changed from`, `not changed from` |
| **Status** | A specific ticket status you've configured (see [Ticket statuses](https://chatbase.co/docs/user-guides/chatbot/help-desk/ticket-statuses.md)). | `is`, `is not`, `is any of`, `is none of`, `changed`, `not changed`, `changed to`, `not changed to`, `changed from`, `not changed from` |
| **Channel** | The channel the ticket came in on: **Helpdesk**, **Chat Bubble/Iframe**, **Email**, **WhatsApp**, **API**, **Messenger**, **Instagram**, **Center Stage**, **Phone**, **Instagram comment**, or **Facebook comment**. Select several at once. Email tickets that a teammate creates in the Helpdesk count as **Helpdesk**, and Help Page conversations count as **Chat Bubble/Iframe**. | `is any of`, `is none of` |
| **Assignee** | Who the ticket is assigned to, including **Unassigned**. | `is`, `is not`, `is any of`, `is none of`, `changed`, `not changed`, `changed to`, `not changed to`, `changed from`, `not changed from` |
| **Team** | Which team the ticket belongs to, including **No team**. | `is`, `is not`, `is any of`, `is none of`, `changed`, `not changed`, `changed to`, `not changed to`, `changed from`, `not changed from` |
| **Tags** | The ticket's [tags](https://chatbase.co/docs/user-guides/chatbot/help-desk/tags.md). Pick **Untagged** to match tickets with no tags. | `contains any of`, `contains none of` |
| **Priority** | The ticket's [priority](https://chatbase.co/docs/user-guides/chatbot/help-desk/priority.md): **No priority**, **Low**, **Normal**, **High**, or **Urgent**. | `is`, `is not`, `is any of`, `is none of`, `changed`, `not changed`, `changed to`, `not changed to`, `changed from`, `not changed from` |
| **Subject** | Keywords in the ticket subject. Add one or more keywords; matching is case-insensitive. | `contains any of` |
| **Description** | Keywords in the ticket description, which is also the ticket's first message. Add one or more keywords; matching is case-insensitive. | `contains any of` |

Two more ticket fields are in the picker:

* **Ticket type**: **Standard ticket**, **Live chat** (tickets from the [Chatbase Live Chat](https://chatbase.co/docs/user-guides/chatbot/actions/chatbase-live-chat.md) Action), or **Outbound**.
* **Last message from**: **Customer** or **Agent**.

> [!NOTE]
>
> What **Description** holds depends on how the ticket was created. For an email ticket it's the email body, and the keyword match runs over the email's HTML. For a takeover or a Chatbase Live Chat ticket, it's the AI summary of the conversation. For a ticket from a create-ticket Action, it's the description the AI agent wrote.

### Contact condition fields

Match on the ticket **requester's** contact record. These look up the person who opened the ticket, so a ticket from an unidentified visitor (no contact record) matches nothing. Contact fields appear under the **Contact** group in the field picker.

| Field | What it matches | Operators |
| - | - | - |
| **Name / Email / Phone number / External ID** | A built-in field on the requester's contact. | `is`, `is not`, `is any of`, `is none of`, `contains any of`, `is set`, `is not set` (Email adds `domain is any of`) |
| **Custom attributes** | Any [custom contact attribute](https://chatbase.co/docs/user-guides/chatbot/contacts/uploading-contacts.md#custom-attributes) you've defined under **Contacts → Manage attributes**, matched against the requester's value. | `is`, `is not`, `is any of`, `is none of`, `contains any of`, `is set`, `is not set` |

### Custom field conditions

When your AI agent has [custom fields](https://chatbase.co/docs/user-guides/chatbot/help-desk/custom-fields.md), they appear in their own **Custom fields** group in the picker, one entry per field. The operators follow the field's type. Dropdown and Boolean fields also support `changed`, `changed to` and `changed from`, and Date fields can be compared with `before`, `after` and `between`.

### Routing condition fields

These describe **how the ticket arrived** (its delivery "envelope"). They only match on the run that creates the ticket or on an inbound customer message, so pair them with a `Ticket is Created` condition and an **Assign team** action to route tickets to teams.

| Field | What it matches | Operators |
| - | - | - |
| **Recipient address** | The support email address that received the ticket. | `is any of`, `domain is any of`, `contains any of` |
| **Recipient phone** | The business phone / WhatsApp number that received the ticket. | `is any of` |

### About operators

| Operator | What it does |
| - | - |
| `is` / `is not` | Compares the ticket's **current** value. For example, "Status category **is** New." |
| `is any of` / `is none of` | Matches when the field is (or is not) one of several selected values. |
| `contains any of` | Matches when the text contains any of the keywords you list (used for **Subject**, **Description**, and text contact fields). For **Tags**, matches when the ticket has any of the listed tags. |
| `contains none of` | For **Tags**: matches when the ticket has none of the listed tags. |
| `domain is any of` | Matches the part **after the `@`** of an address. Used for the contact **Email** field and the **Recipient address** field (for example, route everything from `acme.com`). |
| `changed` / `not changed` | Matches when the field did (or did not) change at all during this update, regardless of the new value. Takes no value. |
| `changed to` / `not changed to` | Matches (or excludes) a specific transition target. For example, "Assignee **changed to** Unassigned." |
| `changed from` / `not changed from` | Matches (or excludes) a specific transition source. For example, "Status **changed from** Open." |
| `before` / `after` / `between` | Compares a Date custom field with a calendar date. |
| `is set` / `is not set` | Matches when a field has (or doesn't have) any value. Takes no value. |

> [!NOTE]
>
> The `changed*` operators only make sense on **updates**: they compare the value before and after the change. On ticket **creation** there's no previous value, so a `changed` condition won't match.

## Actions

Actions are what the trigger does when a ticket matches. Add at least one; they run **in order**, top to bottom.

| Action | What it does |
| - | - |
| **Set status** | Move the ticket to a specific ticket status you've configured. |
| **Set status category** | Move the ticket to a category. This applies the category's **default status**. Tickets already in that category are left unchanged. |
| **Assign team** | Assign the ticket to a team, or to **Default team** (which always follows your current default team, even if you change it later). Optionally check **Auto-assign an agent using the team's strategy** to also route it to an agent based on that team's [assignment method](https://chatbase.co/docs/user-guides/chatbot/help-desk/assignment-algorithm.md). |
| **Assign agent** | Assign the ticket to a specific agent, or choose **Unassign** to clear the assignee. |
| **Set priority** | Set the ticket's [priority](https://chatbase.co/docs/user-guides/chatbot/help-desk/priority.md) to No priority, Low, Normal, High, or Urgent. |
| **Add internal note** | Add an internal note to the ticket. Notes are visible to your team only, never to the customer. |
| **Add tags** | Add one or more [tags](https://chatbase.co/docs/user-guides/chatbot/help-desk/tags.md) to the ticket. Tags it already has are kept. |
| **Remove tags** | Remove the listed tags from the ticket. Tags the ticket doesn't have are ignored. |
| **Set tags** | Replace the ticket's tags with exactly the listed ones. |
| **Remove all tags** | Clear every tag from the ticket. |
| **Send webhook** | Send an HTTP request to an external system. See [Send webhook](#send-webhook). |
| **Send email** | Email the requester, the assignee, a team, a specific agent, or any address, with a subject and body built from ticket fields. See [Send email](#send-email). |
| **Send Slack message** | Post a message to one or more Slack channels, with a body built from ticket fields. See [Send Slack message](#send-slack-message). |
| **Start Slack thread** | Post a ticket card in a Slack channel and keep its thread in sync with the ticket, so your team can reply, add notes, assign, and close from Slack. It needs **Ticket is Created** in the **Match ALL of** group, and a trigger can have only one. See [Slack Ticket Threads](https://chatbase.co/docs/user-guides/chatbot/help-desk/slack-ticket-threads.md). |

No action sets a custom field value.

### Send webhook

The **Send webhook** action posts an HTTP request to an external endpoint, to notify another system, kick off an automation, or sync ticket data.

The action itself is just a **selector**: you pick one of the webhooks you've configured under [**Settings → Webhooks**](https://chatbase.co/docs/user-guides/chatbot/settings.md#webhooks). The endpoint URL, headers, request body, and signing secret all live on the webhook connection, so several triggers can reuse the same one.

![Send webhook action selecting a saved webhook connection](https://mintcdn.com/chatbase/oCLpjHP-qNppTc3V/user-guides/images/help-desk/triggers/send-webhook-action.png?fit=max\&auto=format\&n=oCLpjHP-qNppTc3V\&q=85\&s=18d42303fac0bb00559a7acf4517406b)

* Configure the endpoint, custom headers, and a request body template (with `{{ticket.*}}` placeholders) once under [**Settings → Webhooks**](https://chatbase.co/docs/user-guides/chatbot/settings.md#webhooks), then reference it from as many triggers as you like.
* Each delivery is signed with the connection's secret via an `X-Chatbase-Signature` header so your endpoint can verify it came from Chatbase.
* Webhooks are delivered **after** the ticket change is saved and are retried on transient failures, so your endpoint may receive the same event more than once. Dedupe on the delivery id.

Set up a connection on the [**Settings → Webhooks**](https://chatbase.co/docs/user-guides/chatbot/settings.md#webhooks) page:

![Webhooks configuration page with endpoint, headers, and request body](https://mintcdn.com/chatbase/oCLpjHP-qNppTc3V/user-guides/images/help-desk/triggers/webhooks-configuration.png?fit=max\&auto=format\&n=oCLpjHP-qNppTc3V\&q=85\&s=c15eac044fd38343283cf5e641883966)

### Send email

The **Send email** action sends an email when a ticket matches: to keep the customer posted on a status change, alert a team about a new high-priority ticket, or notify an outside address that doesn't use the Helpdesk.

Everything is configured right on the action: who receives it, the subject, and the body.

![Send email action with recipient, subject, and body fields](https://mintcdn.com/chatbase/mokC64GrzmKRexPw/user-guides/images/help-desk/triggers/send-email-action.png?fit=max\&auto=format\&n=mokC64GrzmKRexPw\&q=85\&s=f54d850ed581de104c852abf12620965)

#### Recipient

| Recipient | Who gets the email |
| - | - |
| **Requester** | The customer who opened the ticket, at the email on their contact record. |
| **Assignee** | The agent the ticket is currently assigned to. Skipped if the ticket is unassigned. |
| **Assigned team** | Every member of the team the ticket is currently assigned to. Skipped if the ticket has no team. |
| **Specific agent** | One agent you choose. |
| **Specific team** | Every member of one team you choose. |
| **Custom address** | Any address you type. This field accepts placeholders, so `{{ticket.requester_email}}` works too. |

Team recipients send **one email per member**. A recipient that can't be resolved to a valid address (an unassigned ticket with an **Assignee** recipient, for example) is skipped without failing the rest of the trigger.

#### Sender and threading

* **From address:** the address the ticket was received on, if it's one of your [Helpdesk emails](https://chatbase.co/docs/user-guides/chatbot/help-desk/email-settings.md). Otherwise the first Helpdesk email, then any verified address, then your AI agent's Chatbase address.
* **From name:** the custom name, if [Display Name](https://chatbase.co/docs/user-guides/chatbot/help-desk/email-settings.md#display-name) is set to **Use custom name**. In the default **Automatically use support associate's name** mode, trigger emails go out with no display name.
* **Threading:** emails to the **Requester** are sent in the ticket's email thread, so the customer's reply lands back on the same ticket. Emails to agents, teams and custom addresses are not threaded.
* **Signature:** your Helpdesk email signature is not added to trigger emails.

#### Subject and body

The **Subject** is a single line and the **Body** is a rich-text editor with formatting, lists, and links. Both accept ticket fields as `{{ }}` placeholders: type `{{` to search and insert one. Placeholders are filled in with the ticket's values at send time, **after** every trigger in the run has finished, so the email reflects the ticket's final state (for example, the status your trigger just set).

| Placeholder | Value |
| - | - |
| `{{ticket.number}}` | Ticket number |
| `{{ticket.url}}` | Link to the ticket in your dashboard |
| `{{ticket.subject}}` | Subject |
| `{{ticket.description}}` | Description |
| `{{ticket.status}}` | Status, agent-facing label |
| `{{ticket.status_external}}` | Status, customer-facing label |
| `{{ticket.status_category}}` | Status category |
| `{{ticket.channel}}` | Channel the ticket came in on |
| `{{ticket.type}}` | Ticket type |
| `{{ticket.priority}}` | Priority |
| `{{ticket.assignee_name}}` | Assignee's name |
| `{{ticket.message_text}}` | Latest message, as plain text |
| `{{ticket.message_html}}` | Latest message, as HTML |
| `{{ticket.requester_name}}` | Requester's name |
| `{{ticket.requester_email}}` | Requester's email |
| `{{ticket.created_at}}` / `{{ticket.updated_at}}` | Timestamps (ISO-8601) |
| `{{ticket.id}}` / `{{ticket.status_id}}` / `{{ticket.assignee_id}}` / `{{ticket.team_id}}` | Raw identifiers, useful when the email is read by another system |

There are no placeholders for custom fields or contact attributes. A placeholder with no value (for example, `{{ticket.requester_name}}` for a contact without a name) is replaced with an empty string. Ticket values are inserted as plain text, so formatting in a customer's message can't alter your email's layout.

> [!TIP]
>
> Use `{{ticket.status_external}}` in emails to customers and `{{ticket.status}}` in emails to your team: they're the customer-facing and agent-facing labels you set under [Ticket statuses](https://chatbase.co/docs/user-guides/chatbot/help-desk/ticket-statuses.md).

> [!WARNING]
>
> Agents replying to a ticket from the dashboard already email the requester through the email channel. A **Send email → Requester** action on **Ticket is Updated** with no other conditions would send the customer a second email on every change. Scope it to what you want them to hear about, for example with a `Status changed to` condition.

### Send Slack message

The **Send Slack message** action posts to Slack channels when a ticket matches, so your team hears about it where they already work instead of having to watch the inbox.

Everything is configured on the action: the channels it posts to (up to 20), and the message itself. It needs the [Slack integration](https://chatbase.co/docs/user-guides/integrations/slack.md) connected first.

> [!NOTE]
>
> For a **private** channel, the Chatbase Slack app has to be a member before it can post. Run `/invite @Chatbase` in the channel.

#### Message

Write the message in the composer. It accepts the same ticket placeholders as [Send email](#send-email): type `{{` to search and insert one, or use the `{ }` button in the toolbar. There is an emoji picker beside it.

Slack messages also take a **fallback**, written with a `|` inside the placeholder. `{{ticket.requester_name | there}}` prints the requester's name, or `there` when the contact has no name, which keeps a greeting from reading as `Hi ,`.

> [!TIP]
>
> **Send Slack message** posts a one-off alert. To handle the ticket from Slack (reply to the customer, add notes, assign, and close), use **Start Slack thread** instead. See [Slack Ticket Threads](https://chatbase.co/docs/user-guides/chatbot/help-desk/slack-ticket-threads.md).

## Checking What a Trigger Did

Each time triggers run on a ticket, the conversation shows one ⚡ entry for that run. It names the trigger and lists every action in the order it ran. Click a trigger's name to open it in the editor.

![A trigger run in the ticket conversation: priority set to High, VIP tag added, email sent to the requester, and a Slack message posted](https://mintcdn.com/chatbase/mfqw4vXv8tQKdbk2/user-guides/images/help-desk/triggers/trigger-run-activity.png?fit=max\&auto=format\&n=mfqw4vXv8tQKdbk2\&q=85\&s=dbc5adb90fe6661e5f4ba2fc1dfe43ed)

Runs with a failed action open expanded so the failure is visible. Other runs start collapsed with a count, like `3 changes`. Click the header to expand or collapse it.

Each action shows its result:

* Field changes show the old and new value, like `Priority  No priority → High` or the tag that was added.
* **Send email** shows the recipient and the subject as it was sent, with placeholders filled in. Expand it to read the body.
* **Send webhook** shows the endpoint and the HTTP status code it returned. The code appears once your endpoint responds, and a retry that succeeds replaces an earlier failure.
* **Send Slack message** shows the channels it posted to.
* A failed action shows in red with the reason, like `Status not changed: the status no longer exists`, `Email not sent: no valid recipient address`, or `Endpoint returned HTTP 500`. The rest of the run still applies.

Internal notes from a trigger appear as their own note in the conversation, credited to the trigger. Changes made by agents or by the system show as single lines outside these entries.

## Managing Triggers

### Ordering

Triggers run in the order they appear in the list. Drag the handle on the left of any trigger to reorder it. Because **every matching trigger fires**, the order matters when two triggers touch the same field: the later one wins.

![Dragging to reorder triggers in the list](https://mintcdn.com/chatbase/XFP5f4YsqhVtBOe3/user-guides/images/help-desk/triggers/reorder-triggers.png?fit=max\&auto=format\&n=XFP5f4YsqhVtBOe3\&q=85\&s=d8fe6f8ff6bc34d2b677aaec9feb2e7d)

### Activate or pause

Use the switch on each trigger row to turn it **Active** or **Paused**. Paused triggers stay in your list but don't run, so you can temporarily disable a rule without deleting it.

### Edit or delete

Open a trigger to edit its name, conditions, or actions at any time. To remove a trigger, use the delete control and confirm. Deleted triggers stop running on new and updated tickets, and this can't be undone.

### Needs attention

If a trigger references something that no longer exists (a deleted team, an archived status, a removed agent, or an archived Slack channel), it's flagged with a **Needs attention** badge. Open the trigger and update the affected condition or action to fix it. A **Start Slack thread** action is also flagged when Chatbase isn't a member of its channel: run `/invite @Chatbase` in that channel.

## Good to Know

* **Every matching trigger fires.** Triggers aren't exclusive: all rules whose conditions match will run, in order. Use ordering to control which action takes precedence.
* **Triggers run after the ticket is saved.** They apply once a create or update is committed, so they never block or fail the underlying ticket change. Webhook and email actions are sent after the save, too.
* **Only active triggers run.** Pause a trigger to disable it without losing its configuration.
* **Triggers are per AI agent.** Each AI agent has its own list, and limits count per AI agent, not per workspace.
* **Triggers need the Helpdesk plan.** If the account's plan no longer includes the Helpdesk, triggers stop running.
* **Triggers route tickets to teams.** Use a `Ticket is Created` condition, a **Recipient address** / **Channel** condition, and an **Assign team** action. Add **Team is No team** so it doesn't override a team set earlier, and place it above **Route to default team** so it runs first.

### Limitations

* No time-based triggers: there's no condition for business hours or for the time since the last message.
* No action sets a custom field, and there are no custom-field or contact-attribute placeholders.

### Limits

| Limit | Value |
| - | - |
| Triggers per AI agent | 1,000 |
| Conditions per group | 50 |
| Actions per trigger | 50 |
| Values per condition | 50 |
| Characters per value | 1,000 |
| Slack channels per **Send Slack message** action | 20 |
| Firings per run | 1,000 |
| Email subject | 300 characters |
| Email body | 50,000 characters |
| Custom email recipient | 320 characters |

When you reach the trigger limit, the page shows "You've reached the limit of 1000 triggers."

## Frequently asked questions

> [accordion] Can a trigger fire when a ticket has had no reply for 24 hours?
>
> No. Triggers run only when a ticket is created or updated, and nothing re-checks tickets over time. There's no condition for business hours or for the time since the last message. To keep an eye on waiting tickets, use a [saved view](https://chatbase.co/docs/user-guides/chatbot/help-desk/saved-views.md) with **Last message by** is **Customer** and an open status, sorted by **Last activity (oldest)**.

> [accordion] Can triggers use priority, tags or custom fields as conditions?
>
> Yes. **Priority**, **Tags**, **Ticket type**, **Last message from** and every custom field are available as conditions, alongside status, channel, assignee, team, subject, description and the requester's contact fields.

> [accordion] How do I email an agent when a ticket is assigned to them?
>
> The Helpdesk only plays a sound in the app when you're assigned a ticket. To also send an email, create a trigger with **Ticket is Updated** and **Assignee changed**, and a **Send email** action to the **Assignee**.

> [accordion] How do I tag every ticket from one company's email domain?
>
> Add a contact **Email** condition with `domain is any of` (for example, `acme.com`) and an **Add tags** action. You can then filter the inbox or a saved view by that tag.

> [accordion] Do triggers run on tickets created through the API or by a takeover?
>
> Tickets created through the API and by teammates in the Helpdesk run **Created** triggers. A manual takeover skips **Created** triggers, including the default team trigger, but the assignment that follows the takeover runs **Updated** triggers.

> [accordion] Can two triggers loop forever?
>
> No. Each trigger fires at most once per run, and a run stops after a full pass in which nothing fires, or after 1,000 firings at most. Changes made by triggers don't start a new run.


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