> For the complete documentation index, see [llms.txt](https://support.suptask.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.suptask.com/working-with-tickets/for-agents-who-respond-and-manage-tickets/how-to-automatically-create-tickets-from-new-messages.md).

# Automatic ticket creation

Learn how to create tickets automatically from new messages

***

Automatic ticket creation turns messages posted in a Slack channel into tickets, without any action from the requester. The message becomes the ticket description.

You decide which messages create tickets:

* **Every new message** - capture everything posted in the channel
* **Only when it matches a rule** - create a ticket only when the message contains a keyword, mentions @Suptask, or both

Rules are useful in busy channels where not every message is a request, for example a team channel where people also chat, or an alerts channel where only some alerts need follow-up.

***

### Enable automatic creation of tickets

Automatic creation is a setting on a Slack channel intake source of your Inbox.

1. Open your Inbox and go to the **Intake sources** tab
2. **Add intake source** of the type **Slack channel** and select the channel, or open an existing source
3. Go to **Creation mode** and select **Automatic**
4. Under **Which messages create new tickets?**, choose **Every new message** or **Only when it matches a rule** (see below)
5. Select the Forms to offer on the source and save

**Good to know:**

* Forms with optional fields can be created without filling in the fields. Forms with required fields will always be prompted to be filled in.
* If several Forms are offered on the source, the requester is asked to select a Form in a reply that is only visible to them.
* The creation mode and its rules are shared by every Inbox connected to the source.

[Learn more about Intake sources](https://support.suptask.com/setup-and-configure/inboxes/intake-sources)

***

### Choose which messages create tickets

| Option                          | What happens                                                                  | Use it when                                                                         |
| ------------------------------- | ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| **Every new message**           | Every new message in the channel becomes a ticket.                            | The channel is only used for requests, such as `#it-helpdesk` or an alerts channel. |
| **Only when it matches a rule** | A ticket is created only when the message matches at least one selected rule. | The channel also has conversations that should not become tickets.                  |

With **Only when it matches a rule**, select one or both rules:

* **Contains a keyword** - the message contains one of your keywords
* **Suptask is mentioned** - the message mentions @Suptask

Messages that don't match a rule are left as regular Slack messages.

***

### Rule: Contains a keyword

A ticket is created when the message contains one of the keywords you add.

1. Tick **Contains a keyword**
2. Type a keyword and press **Enter**. Repeat for each keyword, for example `outage`, `refund`, `urgent`

How keywords are matched:

* **Not case-sensitive** - `urgent` matches *Urgent* and *URGENT*
* **Found inside words** - `it` matches *submit*, and `pay` matches *payroll*

{% hint style="warning" %}
Since keywords are also found inside other words, short keywords can create more tickets than intended. Prefer distinctive words or phrases, such as access request instead of access.
{% endhint %}

***

### Rule: Suptask is mentioned

A ticket is created when someone mentions **@Suptask** in their message, for example:

> @Suptask my laptop won't connect to the VPN

This lets people in the channel decide themselves when a message should become a ticket, while the rest of the conversation stays untouched. Suptask needs to be a member of the channel - [invite the Suptask App](https://support.suptask.com/getting-started/install-suptask/invite-the-suptask-app) with `/invite @Suptask`.

***

### Example setups

| Channel              | Setup                                               | Result                                                             |
| -------------------- | --------------------------------------------------- | ------------------------------------------------------------------ |
| `#it-helpdesk`       | Every new message                                   | Every request posted becomes a ticket.                             |
| `#team-engineering`  | Suptask is mentioned                                | Only messages where someone tags @Suptask become tickets.          |
| `#alerts-production` | Contains a keyword: `critical`, `outage`            | Only critical alerts become tickets; the rest stay in the channel. |
| `#finance-questions` | Contains a keyword: `refund` + Suptask is mentioned | Refund messages and messages that tag @Suptask become tickets.     |

***

### Automatic creation from other Slack apps & bots

Messages posted by other Slack apps and bots in a channel with an Automatic intake source also create tickets. This lets you create tickets from events in other tools, directly in your Slack workspace.

For example, when an alerting app posts in a channel, Suptask creates a ticket so the remediation of the alert can be tracked. Combine it with **Contains a keyword** to only create tickets for the alerts that need action.

{% content-ref url="/pages/xzp2WBZUGYEW9MpKuI5c" %}
[Integrate with any app in Slack](https://support.suptask.com/integrations-automations-and-workflows/integration-guides/how-to-automate-and-integrate-suptask-with-other-slack-apps.md)
{% endcontent-ref %}
