Every request in Serval becomes a ticket. This guide covers the components of a ticket and how to configure them.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.
Accessing Team Settings
To configure ticket attributes for your team, navigate to Settings for your team.Ticket Properties
Each ticket contains configurable properties that control how it’s categorized, prioritized, and routed:Status
Current workflow stage: To Do, In Progress, Done, or Canceled
Priority
Urgency level that determines handling order and SLA timelines
Category
AI-inferred property used for classification and routing
Assignee
Team member or Serval responsible for resolving the ticket
SLA
Time remaining to meet response and resolution commitments
Labels
Custom tags for grouping and filtering
Ticket Type
Classification as Request or Incident
Due Date
Target date for ticket resolution, with overdue indicators
Tasks
Sub-items for breaking down complex tickets
External Links
Connections to synced external ticketing systems
By default, tickets are assigned to Serval. The AI will continue working on the ticket until it either resolves the issue or escalates to a human agent.
Built-in Fields
In addition to configurable properties, every ticket has these built-in fields:| Field | Description |
|---|---|
| Title | Brief summary of the request, auto-generated from the message |
| Description | Full details of the request |
| Requester | The person who submitted the ticket |
| Team | Which team is responsible for handling |
| Due Date | Target resolution date, with overdue indicators when past due |
| Created | When the ticket was submitted |
| Updated | When the ticket was last modified |
Built-in Fields vs Custom Fields
Serval gives you three ways to describe what a ticket is about. They look similar on the surface but serve different purposes — choosing the right one keeps your routing clean and your data useful.| Built-in | Labels | Custom Fields | |
|---|---|---|---|
| Multiplicity | Exactly one per ticket | Any number (including none) | Any number, each with its own type |
| Required | Yes | No | Configurable per field |
| Primary use | Routing, SLAs, filtering | Grouping, search, trends | Forms, automation, integrations |
Built-in fields:
Category, Status, Priority are built-in fields, used to configure routing and SLA, approval, and other policies. These fields exist on every ticket.When to use labels vs custom fields
- Labels — lightweight, cross-cutting tags that don’t affect routing. Use them to flag themes like a specific project, initiative, or known issue.
- Custom fields — structured data entry (dates, numbers, dropdowns, text) for process-specific information that powers forms, approvals, and integrations.
Ticket Detail View
Click any ticket to open the detail view with three main areas:- Conversation Tab - The full thread between requester, Serval, and team members. See Resolving Tickets for how to respond and use Co-pilot.
- Activity Tab - A chronological log of all changes: status updates, reassignments, workflow executions, and SLA events.
- Properties Panel - The right-hand panel displays all ticket properties and allows quick editing. See Updating Ticket Properties for details.
Configuration Guides
Ticket Types
Statuses
Priorities
SLAs
Categories
Assignment
Labels
Tasks
Sync External Systems
Related
Resolving Tickets
Guide to working through tickets
Workflows
Automate ticket handling
Skills
Knowledge base for AI responses
Analytics
Track ticket metrics