> 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/suptask-ai/slackbot-ai.md).

# Slackbot AI

## How to use the Slackbot with your tickets

Suptask is fully integrated with the new Slackbot, Slack's built-in AI agent. Every Suptask ticket lives natively in Slack with the Responder channel connected to your Inbox. This includes the conversation in the message thread, plus the complete form and all of its fields. Because of this, the Slackbot already has the context it needs to understand your tickets.

That means you can ask the Slackbot about your tickets in plain language and get instant summaries, answers, and suggested next steps - without leaving Slack or opening the Web app.

***

### Why this works

The Slackbot can only help with what it can understand. Suptask makes your tickets easy to understand because each ticket is stored as native Slack content:

* **The thread** holds the conversation — the original request and every reply.
* **The form and fields** hold the structured data - status, priority, assignee, requester, and any custom fields your team uses.

The Slackbot reads both. It combines the discussion in the thread with the structured fields, so it can reason about what a ticket is, who owns it, how urgent it is, and how it relates to other tickets. This is what lets you move from searching and clicking to simply asking.

***

### What you can ask the Slackbot

Here are common ways to use the Slackbot with your Suptask tickets:

* **Summarize critical tickets that need attention**\
  Get a quick overview of high-priority or unresolved tickets so nothing important slips through.
* **Find related tickets**\
  Surface tickets that cover the same issue, requester, or topic — useful for spotting duplicates or recurring problems.
* **Find tickets that need action**\
  See which tickets are waiting on a reply, a status change, or a decision from you or your team.
* **List active tickets assigned to you**\
  Check your own open workload at a glance, without opening a dashboard.

***

### How to ask the Slackbot about your tickets

1. **Open the Slackbot** in Slack - send it a direct message.
2. **Ask in your own words.** There are no special commands to memorize. Describe what you need the same way you would ask a teammate.
3. **Refine with follow-ups.** The Slackbot keeps the context of your conversation, so you can narrow results or ask for more detail in your next message.
4. Done! The Slackbot returns the answer directly in Slack.

{% hint style="info" %}
The Slackbot works best when your tickets use clear, consistent fields such as priority, status, and assignee. The more structured your tickets are, the sharper its answers will be.
{% endhint %}

***

### Example prompts

Try prompts like these and adjust them to fit your team:

* `Summarize the most critical tickets that need attention right now.`
* `Which active tickets are assigned to me?`
* `Are there any tickets related to the login outage from this week?`
* `List the tickets that are waiting on a reply from an agent.`
* `Give me a short status update on the open tickets in #it-support.`

***

### What the Slackbot can see, and how it stays secure

The Slackbot only surfaces information you are already allowed to access in Slack. It respects your workspace's permissions and channel memberships, so it will not show you tickets or conversations you could not otherwise see, which is aligned with the Inbox permissions in Suptask.

This means the answers you get are scoped to you. A team member asking the same question may see a different result based on their own access.

{% hint style="warning" %}
The new Slackbot is a Slack feature, and its availability depends on your Slack plan. If you do not see the Slackbot in your workspace, check with your Slack administrator about whether it is enabled for your plan.
{% endhint %}

***

### Tips for getting better answers

* **Be specific.** Mention a channel, a requester, or a time frame to narrow the results.
* **Ask one thing at a time.** Start broad, then drill down with follow-up questions.
* **Reference the ticket thread.** @mention the Slackbot directly inside a ticket thread to ask about that specific ticket.

***

### Learn more

Here are other useful articles to enhance your ticketing experience with Suptask.

{% content-ref url="<https://support.suptask.com/working-with-tickets/for-users-who-submit-tickets/how-to-create-a-ticket>" %}
<https://support.suptask.com/working-with-tickets/for-users-who-submit-tickets/how-to-create-a-ticket>
{% endcontent-ref %}

{% content-ref url="<https://support.suptask.com/getting-started/ticket-submission>" %}
<https://support.suptask.com/getting-started/ticket-submission>
{% endcontent-ref %}