How Assignment Rules Work
When a ticket is escalated from Serval AI to a human agent, the assignment process follows this order:- Assignment rules — Serval evaluates the ticket against your configured rules in order. The first matching rule (top of the list) determines the assignee. Drag rules to reorder them and change which one wins when multiple rules match.
- Default assignment — If no assignment rules match, the ticket is assigned to your default group (if configured).
- Skills — Natural language instructions for how Serval should handle assignment.
- Unassigned — If nothing above applies, the ticket remains unassigned until manually claimed.
Conditions
Each assignment rule has one or more conditions that determine when it applies. All conditions on a rule must match for the rule to trigger.
Most conditions can match on is or is not, so you can route on the absence of a value, such as Priority is not Low or escalations that land outside a business-hours schedule. The Requester group condition matches on membership only, with no is not variant.
Actions
When an assignment rule’s conditions match, Serval assigns the ticket based on your configured users and groups.Assign to users or groups
Directly assign the ticket to specific users, or to one assignment group.- Users — When multiple users are selected, they form a single pool and Serval picks one assignee.
- Group — The ticket’s owning group is set to that group. How (or whether) an individual member is chosen depends on the workspace’s Group member assignment setting (Round-robin or Human triage).
Requester exclusion
When evaluating candidates from assignment rules or default assignment, Serval automatically excludes the ticket’s requester from the pool. This prevents a ticket from being auto-assigned back to the person who submitted it after escalation. If every candidate in the pool is the requester (for example, a default assignment group with only one member who is also the requester), the ticket is left unassigned.You can always manually assign a ticket to its requester if needed. Requester exclusion only applies to automatic assignment.
Default Assignment
In Workspace Settings → Assignment → Assignment rules, every workspace has a default assignment setting that acts as a fallback when no assignment rules match:- Unassigned: Tickets remain unassigned until someone manually claims them.
- Default group: Tickets are automatically assigned to a specific group.
- Single user: Tickets are automatically assigned to one specific user.
Creating an Assignment Rule
1
Open assignment settings
Go to Workspace Settings → Assignment → Assignment rules.
2
Add a rule
Click Add Rule to open the rule builder.
3
Define conditions
Add one or more conditions. Choose the condition type (category, priority, ticket type, status, schedule, requester group, or requester’s field) and select the matching value. All conditions must be true for the rule to trigger.
4
Choose an action
Select Assign to users/groups, then choose the users or groups that should receive matching tickets.
5
Save the rule
Click Save to activate the rule.
Managing Rules
Rules start collapsed so you can scan their order and destinations. Select a rule’s condition summary to expand or collapse its details. A +N badge indicates additional conditions or actions. Use Expand all or Collapse all above the list to review several rules at once. Switch between List and Tree above the rules. List is the editable view. Tree shows the same rules as a read-only flow diagram that combines neighboring rules into shared decisions, so you can follow how a ticket moves through the rules top to bottom. Select a rule or assignment in the tree to inspect it, then switch back to List to make changes. The three-dot menu remains available while a rule is collapsed. Select Add Rule in the Assignment flow header to add another rule. The Fallback assignment card below the rules handles requests that do not match a rule. Open the Settings tab to manage assignment groups and their work schedules, the custom escalation workflow, and assignment preferences.Editing a Rule
Open the three-dot menu on a rule card and select Edit routing rule to modify its conditions or actions.Reordering Rules
Hover over the number inside a rule card to reveal its drag handle, then grab the handle to drag it up or down. Rules are evaluated top to bottom, so the rule closest to the top wins when more than one rule matches a ticket. Use this to set precedence when rules overlap, for example a “during business hours” rule above an “outside business hours” rule when their schedules touch.Deleting a Rule
Open the three-dot menu on a rule card and select Remove routing rule. A confirmation prompt appears before the rule and all its conditions and actions are removed.Simulate assignment
Use Simulate with Catalyst on Workspace Settings → Assignment to build a reusable ticket simulation. Catalyst asks about the situation and requester, then helps you review and run the scenario using the existing simulation engine.1
Describe the situation
Click Simulate with Catalyst to start a new chat. Describe the request or problem you want to test and identify the requester.
2
Choose the intake
Web is the default. You can also choose an email mailbox, Slack or Microsoft Teams channel, or direct-message connection available to the workspace. Choose the specific mailbox or channel when prompted, since assignment conditions can depend on where the ticket arrived.
3
Review and run
Review the simulation Catalyst creates, including the expected escalation and assignment outcome, then run it. Ticket properties are inferred from the conversation using the workspace’s normal settings. You do not need to preset status, priority, or ticket type.
4
Inspect the outcome
The transcript records category, labels, status, priority, ticket type and custom fields, along with whether the ticket escalated and the selected user or group. Inference follows the workspace’s enabled settings; disabled inference retains normal defaults.Built-in escalation evaluates assignment rules in order, then fallback assignment. If no rule or fallback selects an owner, the result shows Unassigned. Expected-result evaluation uses the recorded ticket state to check the outcome.
Simulated assignment does not notify assignees or advance live assignment rotation. Workflows are mocked unless you explicitly enable live execution when configuring the run.
Related
Assignment groups
Own tickets by org group and choose round-robin or human triage
Categories
Define ticket categories used as assignment rule conditions
Schedules
Configure business hours schedules used in assignment rule conditions
Workspace Routing & Assignment
How tickets get to the right workspace and person

