Skip to main content
This guide walks through the process of resolving tickets in Serval, from finding open tickets to closing them out.

Finding open tickets

Start by locating tickets that need your attention.

In the web interface

  1. Navigate to Tickets in the sidebar
  2. Use the “Involves” filter to find tickets assigned to you
  3. Filter by status (for example, “Open” or “In Progress”) to see active tickets
The “Involves” filter shows all tickets where you’re the assignee, requester, commenter, mentioned, approver, or task assignee. Use it to find everything you’re connected to.

In Workspace Inbox channels

If your support team has configured a Workspace Inbox channel in Slack, tickets in its Serval workspace automatically appear as threads there. This provides a centralized place to triage requests without switching to the web app.
Workspace Inbox channels are private Slack channels where all escalated tickets for your workspace appear. See Configure Workspace Inbox Channels for setup instructions.

Ways to resolve tickets

There are a few ways to resolve tickets in Serval. Choose the method that best fits the situation.

1. Manually resolve

Respond directly to the requester with answers, updates, or follow-up questions. Communicate with the requester and your team in the Activity thread. Forwarded messages (for example, from Slack) show a Forwarded message from line below the quoted content. When a ticket has no draft, the composer collapses to a single-line reply bar so more of the conversation stays in view. Click the bar, press R to reply or I for an internal note, or drag a file onto it to open the full composer. Sending, pressing Esc in an empty composer, or the collapse button returns it to the bar. Drafts, attachments, and CC recipients are kept as it collapses.

Public response

Visible to the requester. Use for:
  • Answering questions
  • Requesting more information
  • Providing updates
  • Confirming resolution

Internal note

Only visible to workspace members. Use for:
  • Documenting investigation steps
  • Sharing context with teammates
  • Handoff information when reassigning
  • Notes that shouldn’t be shared with the requester
Internal note toggle

Internal note toggle in the reply chat

Click the sticky-note icon in the chat to switch to an internal note before typing.

Translate the conversation

When a ticket comes in a language you don’t read, translate it without leaving the ticket.
  • A single message: Open the message’s actions menu and choose Translate. Above the translated text, open the language menu to translate that message into another language. Select Show original to switch back to the source text, then Show translation to return to the translation without waiting for another request.
  • The whole thread: Open the ticket’s More actions menu and select Translate thread to translate every eligible message into your interface language. If some messages couldn’t be translated, the control offers Retry thread translation. Translating the thread also restores messages you’ve switched back to their originals.
Translation starts in your interface language. Changing a message’s translation language affects only that message in your current ticket view; it doesn’t change your interface language, other messages, or what anyone else sees. The original text is preserved. Translation is available to workspace members with permission to translate tickets, which the Read-Only Agent role and above include.

2. Run existing help desk workflows

Automate actions directly from a ticket using organization-wide workflows.
  1. In the reply chat, type / or select Trigger a workflow (the / button). The button opens the workflow menu at the end of your draft, including after a mention or image.
  2. Select from available Help Desk workflows
  3. Fill in any required inputs
  4. Execute the workflow
Slash command to trigger workflow

Running a workflow from ticket chat

Workflow progress and results appear in the Activity timeline.
Help Desk workflows are available to all users in your workspace and are designed for common support scenarios like password resets, software access requests, and IT troubleshooting.

AI agent after escalation

When a ticket is escalated to a human agent, Serval’s AI agent can remain active on the ticket. The AI continues to provide guidance, suggest knowledge base articles, and assist with resolution even while a human is working the ticket. This is configurable per workspace in Workspace Settings.

3. Open Copilot to run workspace-only workflows

Use Copilot to access workspace-only workflows and get AI assistance for resolving tickets. Copilot uses context from your connected identity providers to enrich responses. It can retrieve a user’s department, job title, manager, and other organizational details automatically so you spend less time looking up user information. Copilot is your AI assistant for resolving tickets faster. Click Open Copilot above the reply chat to:
  • Run workspace-only workflows that aren’t available through the / command
  • Draft responses based on ticket context and your knowledge base
  • Summarize long ticket threads
  • Find information in your Skills and knowledge base
  • Get suggestions for next steps or escalation paths

How to use Copilot

  1. Open a ticket
  2. Click Open Copilot above the reply chat
  3. Ask what you need:
    • “Run the employee offboarding workflow for john@company.com”
    • “Draft a response explaining our refund policy”
    • “Summarize this ticket”
    • “What workflows can help with this?”
    • “Find a Skill about password resets”
  4. Review and edit the response
  5. Send or use the suggestion
Workspace-only workflows are restricted to workspace members and are ideal for internal operations, sensitive data handling, and administrative tasks. They don’t appear in the standard / workflow menu but can be accessed through Copilot.
Copilot uses your workspace’s skills and knowledge base. The more skills you add, the better Copilot performs.

Close tickets

When the requester’s issue is resolved:
  1. Send a final response confirming resolution
  2. Update status to a “Done” status (for example, Resolved or Completed) - see Updating Ticket Properties for how to change status
  3. The requester may receive a feedback request
Include a brief summary of what was done in your closing response. This helps if the ticket needs to be referenced later.

Delete archived tickets

If you have permission to delete tickets in the workspace, you can delete them directly from the archive:
  1. Open the workspace’s Settings and select Archives.
  2. On the Tickets tab, select up to 100 tickets.
  3. Select Delete in the selection toolbar.
  4. Review the confirmation, including any child tickets, and confirm Delete.
Deleted tickets move to Recently Deleted. You can select Undo in the confirmation notification to restore them. You can turn ticket deletion off for a workspace. In the workspace’s Settings, open Recently Deleted and switch the Ticket Deletion toggle off (this requires permission to manage workspace settings). While deletion is off, the delete controls are unavailable and no tickets can be moved to Recently Deleted. Turning it back on resumes the automatic cleanup of tickets already in Recently Deleted.

Quick reference


Updating Ticket Properties

Change status, priority, assignee, and labels

The Serval Ticket

Learn about all ticket properties and views

Workflows

Learn about workspace-only and organization-wide workflows

Workspace Inbox Setup

Configure Workspace Inbox channels in Slack