Numbers you can act on.Reporting for tickets, conversations and deals.
Reporting covers tickets or conversations over any date range: what came in, how fast your team answered and resolved it, where it came from, who handled it, and how your pipeline is moving.
Reporting
Issue overview
How much came in, how fast it was handled, and how it compares with the previous period of the same length.
Total issues
447
8%vs previous period
Solved within 7 days
86%
4%vs previous period
Avg. touches per issue
2.4
11%vs previous period
Still open
24
17%vs previous period
Median first response
14m
22%vs previous period
Median time to resolution
5h 40m
9%vs previous period
Median handle time
1h 52m
assignment → resolution6%vs previous period
Reporting in short.
- Where
- Reporting in the sidebar, and an Analytics tab on every client, company and tenant.
- Who
- Owners and admins. Reporting is hidden from members and its data is refused for them.
- Report on
- Tickets or Conversations, switched with one toggle.
- Timeframe
- Last 7, 28 or 90 days, or a custom range, bucketed by day, week or month. Opens on the last 28 days.
- Filters
- Source, tag and assignee. Clicking a breakdown row filters the whole page.
- Comparison
- Each headline number against the previous period of the same length.
- In chat
- Ask ⌘L, Slack or an MCP client for numbers. ⌘L and Slack can also build a PDF report.
Volume and speed, compared with the last period
- Total issues, Still open and Solved within 7 days, with a created-versus-resolved chart for the period.
- Median first response counts the first human reply: the first public comment on a ticket, or the first message from your team after the customer’s first message in a conversation.
- Median time to resolution runs from creation to close. Median handle time runs from assignment to resolution.
- Avg. touches per issue counts human work: comments plus status and assignee changes on tickets, messages sent by your team in conversations.
- Conversation status history is tracked from the day tracking was turned on, so resolution and time-in-status figures for conversations only cover activity since then. The page says so when you switch to Conversations.
Where issues come from
- Sources are the channels: Web widget, Email, WhatsApp, Instagram, Viber and Slack. Tickets add Created manually and API.
- Top customers ranks the clients raising the most issues, linking reporting back to the CRM.
- Avg. time in status shows which of your statuses issues wait in longest.
- The heatmap lays issues out by hour and weekday in your own time zone, which is where staffing questions get answered.
Where issues come from
Volume by source, tag, assignee and customer, when issues arrive, and how long they sit in each status. Click a row to filter the whole page.
- Web widget182
- Email121
- WhatsApp64
- Created manually48
- Billing96
- Bug88
- Feature request71
- Onboarding44
- Ana Kovač141
- Luka Marić118
- Marko Ilić97
- Iva Perić62
- Northwind34
- Kaltbach Energie27
- Harbourside19
- Fjordline15
- Backlog31h
- Todo9h
- In progress6h
- In review4h
Team performance per assignee
- A stacked chart gives the top assignees their own color and folds the rest into Other.
- The table lists total, resolved, a column per source, average touches, and the medians for first response, resolution and handle time.
- Click an assignee to filter the rest of the page to their issues.
Team performance
Per-assignee volume and speed. Issues are attributed to whoever is assigned at the time of closing.
Volume over time per assignee
| Assignee | Total issues | Resolved | Web widget | Created manually | API | Avg. touches per issue | Median first response | Median time to resolution | Median handle time | ||
|---|---|---|---|---|---|---|---|---|---|---|---|
| AKAna Kovač | 141 | 136 | 58 | 38 | 20 | 15 | 10 | 2.1 | 9m | 4h 12m | 1h 31m |
| LMLuka Marić | 118 | 112 | 48 | 32 | 17 | 13 | 8 | 2.6 | 17m | 6h 05m | 2h 10m |
| MIMarko Ilić | 97 | 93 | 40 | 26 | 14 | 10 | 7 | 2.9 | 21m | 7h 44m | 2h 38m |
| IPIva Perić | 62 | 59 | 24 | 17 | 9 | 7 | 5 | 2.3 | 12m | 5h 20m | 1h 47m |
| Unassigned | 29 | 23 | 12 | 8 | 4 | 3 | 2 | 1.2 | 48m | 1d 2h | · |
Sales pipeline from your deal stages
- Open pipeline, Weighted forecast by stage probability, Won with a trend line, and Win rate with average deal size, average cycle and lost value.
- A stage funnel you can switch between count and value, with a table of how many deals are in each stage now, how many reached it and the conversion from the stage before.
- A Client funnel above it shows how people acquired in the period move from Visitors to Interacted to Identified.
Sales pipeline
Deals created in the selected timeframe: how they move through your stages, what is open, and what closed.
Open pipeline
€136.4K14 deals
Weighted forecast
€50.2Kby stage probability
Won
€61K5 deals
Win rate
71%5 won · 2 lost
- Avg. deal size
- €12.2K
- Avg. cycle
- 34 days
24
15
10
7
5
| Stage | In stage now | Reached | From previous |
|---|---|---|---|
| Lead10% | 6€38K | 24€214K | · |
| Qualified30% | 4€52K | 15€168K | 63% |
| Proposal60% | 3€31.5K | 10€122K | 67% |
| Negotiation80% | 1€14.9K | 7€86K | 70% |
| Won100% | 5€61K | 5€61K | 71% |
What customers ask, and what the AI could not answer
- Knowledge gap queue: questions the AI could not confidently answer, ranked by how often they came up, so you know what to document next.
- Knowledge base usage: the most referenced articles, comparing cited (delivered to the customer) with searched, and the articles never referenced in the window.
- Question type breakdown: what conversations were about, useful for spotting a spike after a release.
- Visitor insights from the chat widget: countries, cities, time zones, browsers, operating systems, devices, referrers, ISPs and languages.
Ask for the number instead of opening the page
- Queries cover tickets or conversations over 7, 28, 90 or 180 days, with totals, medians, period-over-period changes and one breakdown: source, tag, assignee, customer, status or hour.
- A summary tool returns the dashboard view in one call: queue, response and resolution times, volume, the client funnel, knowledge gaps, document usage and question types.
- In ⌘L and Slack, Starko can build a PDF report with KPI tiles, a created-versus-resolved chart and the breakdown table, delivered as a download card.
FAQAbout Reporting.
Connect a channel and a repository
Turn the support queue into a build queue.
Feedback starts flowing in minutes. The first recommendation shows up as soon as a pattern repeats, and the first pull request as soon as you accept one.