Understanding Statuses
Every ticket has a status that indicates its current state. Statuses are organized into four categories, and can be completely customized to fit your company’s needs.To Do
Tickets waiting to be started
In Progress
Tickets actively being worked on
Done
Completed tickets
Canceled
Tickets closed without resolution
- Investigating
- Waiting on Customer
- Waiting on Vendor
- In Review
Creating Statuses
1
Open workspace settings
Navigate to Workspace Settings → Statuses.
2
Add a new status
Click Add Status.
3
Configure the status
Fill in the status details:
4
Save
Click Create to add the status.
Default Status
Every workspace must have a default status in the “To Do” category. New tickets are automatically assigned this status. To change the default:- Go to Workspace Settings → Statuses
- Find the status you want as default
- Click the … menu and select Set as Default
AI Status Assignment
Serval’s AI can automatically assign statuses based on ticket content and conversation:- New tickets - AI assigns initial status based on the request
- Updates - AI may suggest status changes based on conversation (e.g., moving to “Waiting on Customer” after asking a question)
Enabling AI Assignment
Toggle AI status assignment in workspace settings:- Go to Workspace Settings → Statuses
- Enable AI status assignment
- Provide detailed status descriptions for best results
AI suggestions appear as recommendations. Workspace members can always override with manual selection.
Status Transitions
Change ticket status from list view, detail view, or chat. See Updating Ticket Properties for detailed instructions.Automatic Transitions
Configure automatic status changes:On ticket creation
On ticket creation
New tickets automatically get the default “To Do” status.
On resolution
On resolution
When a ticket is resolved (via AI or manually), it moves to a “Done” status.
Via workflows
Via workflows
Workflows can automatically update ticket status as part of their execution.
Transition rules
By default, a ticket can move from any status to any other. To constrain the allowed moves for a ticket type (Request, Incident, or Problem), open it under Workspace Settings → Ticket types and click Enable transitions. Serval seeds a starter state machine so no ticket is ever stranded; edit it to set which statuses can move to which, optionally gating a transition on built-in or custom fields. Once on, transitions are enforced everywhere a status changes for people, AI, and workflows alike: Serval’s AI proposes only valid next statuses, pickers gray out disallowed moves, and rule-breaking manual updates are blocked (Serval won’t let you remove a transition that would strand live tickets). Click Turn off transitions to lift the constraints. Change models keep their built-in ITIL lifecycle regardless. Tasks share one status set that you edit on the Task ticket type. Tasks of the built-in Task type can move to any task status, and each custom task type picks the statuses it uses and its own transitions.Locking statuses
Mark a Done or Canceled status as locked to stop a ticket accepting new requester replies once it reaches that status. Open Workspace Settings → Statuses, find a status in the Done or Canceled category, and turn on Locked. Only those two categories can be locked. While a ticket sits in a locked status:- Requesters can’t reply. The web reply composer becomes a closed-ticket notice, and replies sent from Slack or Microsoft Teams are dropped with a notice that the ticket is no longer accepting replies.
- Workspace members can still add internal notes, and Serval’s AI stops suggesting status changes and won’t move the ticket out of a locked status on its own.
- Moving the ticket to an unlocked status (manually) reopens it to replies.
Status Best Practices
Use action-oriented names
“Awaiting Customer Response” is clearer than “Pending”
Keep the list short
5-8 statuses per category is usually sufficient. Too many creates confusion.
Match your workflow
Statuses should reflect actual stages in how you handle tickets
Write good descriptions
Detailed descriptions improve AI accuracy and help team members choose correctly
Example Status Configurations
IT Help Desk
IT Help Desk
To Do: New, TriagedIn Progress: Investigating, Waiting on User, Waiting on Vendor, Implementing FixDone: Resolved, Resolved - Known IssueCanceled: Duplicate, Cannot Reproduce, Won’t Fix
HR Requests
HR Requests
To Do: New RequestIn Progress: Under Review, Pending Approval, ProcessingDone: Completed, FulfilledCanceled: Withdrawn, Denied
Facilities
Facilities
To Do: New RequestIn Progress: Scheduled, In Progress, OrderedDone: CompletedCanceled: Canceled
Editing and Deleting Statuses
Edit a Status
- Click the … menu on the status
- Select Edit
- Update name, category, or description
- Save changes
Delete a Status
- Click the … menu on the status
- Select Delete
- Confirm deletion
You can delete the last status in a category when nothing references it, but each ticket type must retain at least one status. The four categories remain, even when empty. You cannot delete the default status: set a different default first. If tickets, rules, ticket type lifecycles, or transitions reference a status, move or remove those references before deleting it.
Related
Updating Ticket Properties
Learn how to change ticket status from list view, detail view, or chat
The Serval Ticket
Understand all ticket properties and configuration options

