> ## Documentation Index
> Fetch the complete documentation index at: https://docs.serval.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Slack
> Complete reference for all interaction methods, thread management, workflows, and advanced features
Serval provides intuitive ways to interact directly from Slack, making it easy to create tickets, trigger workflows, and get help without leaving your conversations. This guide covers all the available interaction methods.
## Overview
Type commands like `/serval help` from any channel or DM
Create a ticket from an existing Slack message
Tag @Serval in channels to activate assistance
Continue conversations naturally in threads
For support teams: Centralized view of all tickets
Private one-on-one conversations with Serval
## Slash Commands
### /serval Command
The quickest way to create a ticket from anywhere in Slack:
```text theme={null}
/serval help [your request message]
```
**When to use:** At any time, especially when you prefer creating a quick & simple ticket.
**Example - Access request:**
```text theme={null}
/serval help I need access to AWS for today
```
The `/serval` command works anywhere in Slack as long as Direct Messaging is enabled by your Serval administrators.
## Message Actions
### Creating Tickets from Existing Messages
Sometimes the perfect ticket description is already in a Slack message. You can turn any message into a ticket using Slack's message actions:
1. Hover over any message in Slack
2. Click the three dots (...) menu
3. Select "More message shortcuts..."
4. Choose "Create a ticket" using Serval from the list of actions
**Benefits:**
* No need to retype or copy/paste existing messages
* Works on any message in any channel
## Mentions in Channels
### Activating Serval with @mentions
In channels where Serval is present, you can activate help by mentioning @Serval:
**How it works:**
* In Help Desk channels: Serval automatically monitors and responds to all new threads
* In Silent Mode channels: @Serval activates assistance for that thread
* In Team Only channels: Behaves similarly to Help Desk channels, but does not escalate to a human. It will always stay engaged
**Example - Getting help:**
```text theme={null}
@Serval can you help me reset my password?
```
**Example - Triggering a workflow:**
```text theme={null}
@Serval please run the new user onboarding workflow for jane@company.com
```
## Thread-Based Interactions
### Working Within Threads
Serval maintains context within Slack threads, making conversations natural and efficient:
**Best practices:**
* Keep related discussion in the same thread
* Serval remembers context from earlier in the thread
* You can ask follow-up questions naturally
* Upload files, images, or logs directly in the thread
### Status Updates via Emojis
Serval uses emoji reactions to communicate status at a glance:
**Common status emojis:**
* ⏳ Serval is working on it
* ✅ Successfully completed
* ❌ Cancelled
## Direct Messages (DMs)
### Private Support Conversations
For sensitive requests, you can DM Serval directly:
**When to use DMs:**
* Personal or sensitive requests
* Private troubleshooting sessions
Your Serval administrator must enable Direct Messaging for this to work. This is done within the Slack application at the team level. Note that any Serval administrator will be able to view your support ticket, but others in your Slack workspace will not.
## Team Inbox Channels
A dedicated private channel for Serval Managers and Agents to triage all tickets created for your team, without switching to the web interface.
**Key benefits:**
* Triage all tickets in one place, right from Slack
* Collaborate with other agents on ticket resolution
* Respond to end users directly—replies sync back to their original location
Team Inbox channels are designed to be triage-only, meaning new messages posted to the channel won't create new tickets. Use `/serval help`, DMs, or help desk channels to create new tickets.
### Working with Team Inbox
* **View**: Each ticket appears as a thread with details and history
* **Respond**: Reply in threads—messages send to end users automatically
* **Manage**: Use commands like `@Serval assign to me` to pick up and handle escalated tickets
**Learn more:** For complete setup instructions, see [Configure Team Inbox Channels](/sections/integrations/slack#configure-team-inbox-channels).
## Advanced Interactions
### Workflow Triggers
Trigger Serval workflows directly from Slack:
**Example commands:**
* "Run the employee onboarding workflow for [john@company.com](mailto:john@company.com)"
* "Execute the AWS access grant workflow for the engineering team"
* "Start the offboarding process for the contractor"
### Transfer Tickets by Tagging @Serval
Move a ticket to another team by mentioning @Serval in a message and requesting the transfer. For example:
```text theme={null}
@Serval transfer this ticket to the Security team
```
Only members of the ticket's current team can perform transfers. After the transfer, the receiving team takes ownership of the ticket.
### Manual Escalation
Use the manual escalation button on the ticket card in Slack to escalate a ticket directly to a human agent without AI involvement. This bypasses the help desk agent entirely and routes the ticket to your team's triage queue.
### Ticket Management
Update and manage tickets without leaving Slack:
**Available actions:**
* "Set priority to high"
* "Assign this to @teammate"
* "Close this ticket"
* "Change status to in progress"
## Quick Reference
| Method | Where it works | Best for |
| ---------------------- | -------------------- | ---------------------------------------- |
| `/serval help` command | Anywhere in Slack | Quick ticket creation |
| Message actions (...) | Any message | Converting existing messages to tickets |
| @Serval mention | Channels with Serval | Activating help in a thread |
| Thread replies | Active threads | Ongoing conversations |
| Direct messages | Serval DM | Private requests |
| Team Inbox | Team Inbox channel | Support agents triaging all team tickets |
## Ticket Status in Slack
Serval displays dynamic ticket status updates directly in Slack messages. As a ticket progresses — from creation through workflow execution to resolution — the status UI in the Slack message updates in real time so you can track progress without leaving Slack.
***
## Welcome Message for New Users
When a new user interacts with Serval for the first time in Slack, they receive a welcome message in the Messages tab introducing Serval's capabilities. This message explains how to get help, what they can ask, and where to find support.
***
## Tips for Success
Include relevant details like user emails, system names, error messages, or links to help Serval take accurate action.
Keep related messages in the same thread so Serval maintains full context of the conversation.
Serval understands conversational requests - no need to use special syntax or formatting.
Quick visual feedback helps you understand Serval's progress without reading every response.
## Troubleshooting
### Serval isn't responding
**Check these common issues:**
1. Is Serval added to the channel? (Look for @Serval in the member list)
2. Is the channel configured in Serval? (Check your Slack integration settings)
3. For new channels, try @mentioning Serval to add it
4. Ensure your Slack workspace is properly connected to Serval
### Commands not working
If slash commands aren't appearing:
1. Refresh Slack (Cmd/Ctrl + R)
2. Check that your workspace admin has approved the Serval app
3. Try typing `/serval` fully - it should auto-complete
4. Contact [support@serval.com](mailto:support@serval.com) if issues persist
## Related Documentation
* [Slack Quickstart](/sections/documentation/end-user/slack-quickstart) - Quick-start guide for end users
* [Slack Integration Setup](/sections/integrations/slack) - Administrator configuration guide
* [Ticketing Overview](/sections/documentation/ticketing/overview) - Understanding tickets
* [Workflow Automation](/sections/documentation/workflows/overview) - Workflow documentation