Assignment rules and SLA policies
Assignment rules decide who gets a new ticket. SLA policies decide how fast it must be answered and resolved, and what happens when it is not. Together they keep tickets from sitting unseen.
Assignment rules
Open Settings → Assignment rules. Starko routes every new ticket through the enabled rules in order; the first rule that matches assigns the ticket. Tickets nobody can take wait on their team's queue until someone frees up.
settings assignment
Press New rule to add one.
Match on priority, tags, team, project or channel.
Assign to one person, a team with round-robin or least-busy distribution, or the ticket's project lead.
Capacity caps how many open tickets a person holds before the rule skips them.
Toggle a rule off to pause it without deleting it.
Rules apply to tickets created by customers, by the assistant, by workflows and by your team. A ticket created with an assignee already chosen is left alone.
Teams
Rules route to teams as well as people. Create teams under Settings → Team and add members; a team can also be set on a ticket by hand with the team chip.
SLA policies
Open Settings → SLA policies and press Manage policies. A policy sets a first-response target and a resolution target for the tickets it matches.
settings sla policies
Match by priority, tags, team, project or tenant, so a key account gets a tighter target.
Business hours make timers pause outside the schedules you set under Settings → Business hours, so evenings, weekends and holidays do not count against targets.
Warnings notify the assignee before a breach. Escalation reassigns or notifies a manager after one.
New matching tickets are tracked within ten minutes of creation.
Watching SLAs
The SLA page (under Tickets in the sidebar) lists active timers with time remaining, and Reporting shows breach rates over time.
sla page
Ask Starko (⌘L) "which tickets are about to breach" for the same information in chat, or from Slack and your MCP-connected tools.
Did this answer your question?