How tickets flow through Starko
Tickets are how a customer's problem becomes a change your team ships. This article explains where tickets come from, how they are routed and what closes them.
Where tickets come from
Conversations. The support assistant opens a ticket when a customer asks for a person, when it cannot answer, or when a procedure tells it to. Your team can also create a ticket from any thread.
Email. Messages to your support address become conversations; those that need work become tickets.
Your team. Press Create Ticket on a board, use ⌘K, or ask Starko (⌘L) to create one.
Workflows and integrations. Ticket workflows can create tickets on a schedule or an event, and GitHub issues sync both ways for projects that enable it.
Starko AI. After a run, Starko AI files what it learned about your repository as small tickets tagged repo-learnings.
Status and groups
Every ticket has a status, and every status belongs to a group: Backlog, Unstarted, Started, Completed or Cancelled. Groups drive time tracking, reporting and when a ticket counts as closed. The default statuses are Backlog, Open, In Progress, In review and Closed; you can rename, reorder and add your own under Settings → Ticket statuses.
settings statuses
Routing
When a ticket is created, assignment rules pick an assignee based on priority, tags and team, and balance load across the team. Tickets nobody can take wait on their team's queue. SLA policies start response and resolution timers, warn before a breach and escalate after one.
Working the ticket
The assignee sees the ticket in their Inbox and on the board.
For code changes, they press Fix with Starko AI or mention @starko. The agent opens a draft pull request with evidence.
For customer questions, they reply from the ticket. The reply goes back through the customer's channel.
Internal comments, time tracking, relations and attachments keep the context in one place.
tickets board
Closing
Move the ticket to a status in the Completed group. Starko can tell the customer the ticket is resolved, the timer stops, and the ticket leaves the Inbox. Auto-close moves stale tickets to a status of your choice after a period you set, and auto-archive archives closed tickets after a month. Both are under Settings → Ticket statuses and are attributed to "Automation" in the activity log.
Views
Boards, lists, charts and timelines over the same tickets are described in Boards, lists, filters and saved views.
Did this answer your question?