Extensions
Flows and routing
A flow is for work that arrives as a stream: support, a service unit, a legal department with routine requests. Everyone else never sees it.
Available in:Extension, added separately from the plan
What it covers
- Routing rules: round robin, by load, by qualification, first to take it
- Pulling a task from the shared queue and moving tasks between flows
- A flow SLA: target response and resolution time, escalation on breach
- A waiting time forecast from current throughput
- Metrics: throughput, time in queue, lead time and cycle time
- The median sits next to the average: one long ticket distorts an average
Frequently asked questions
Who needs flows?
Teams that receive tasks as a stream: support, a service department, a legal team with typical requests. The extension stays hidden for everyone else.
How does a task find its assignee?
By the flow rule: by turn, to the least loaded person, by skill or to whoever takes it first. An SLA breach shows at once and is escalated.
Where it helps
Other features
Put a number on your first project
Tasks, projects, boards, dates and time tracking are available on the free tier. Rates, cost and profitability switch on when you need figures rather than discipline alone.