Starko

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.

v2.starko.one/dashboard/analytics
Reporting
72%

Reporting

TicketsConversationsLast 28 days 6 Oct to 2 NovDayWeekMonthAll sourcesAll tagsAll assignees

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 → resolution

6%vs previous period

Issue volume over timeCreated 447 · Resolved 423
6 Oct13 Oct20 Oct27 Oct2 Nov
Created Resolved
At a glance

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.
Issue overview

Volume and speed, compared with the last period

The top of the page answers two questions: how much came in, and how fast it was handled. Every tile shows the change against the previous period of the same length, with the arrow colored by whether the change is good or bad.
  • 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.
Breakdowns

Where issues come from

Breakdowns rank volume by source, tag, assignee and customer, show how long issues sit in each status, and map when they arrive. Each row is a filter: click a tag and every number on the page narrows to that tag.
  • 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.
v2.starko.one/dashboard/analytics
Reporting
72%

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.

By sourceIssues
  • Web widget182
  • Email121
  • WhatsApp64
  • Created manually48
By tagIssues
  • Billing96
  • Bug88
  • Feature request71
  • Onboarding44
By assigneeIssues
  • Ana Kovač141
  • Luka Marić118
  • Marko Ilić97
  • Iva Perić62
Top customersIssues
  • Northwind34
  • Kaltbach Energie27
  • Harbourside19
  • Fjordline15
Avg. time in statusTime spent
  • Backlog31h
  • Todo9h
  • In progress6h
  • In review4h
By time of day and day of weekLocal time (Europe/Berlin)
MonTueWedThuFriSatSun
0:00
4:00
8:00
12:00
16:00
20:00
Team

Team performance per assignee

Team performance shows each assignee’s volume over time and a table of their totals and speed. Issues are attributed to whoever is assigned when the issue closes, so a handover counts for the person who finished the work.
  • 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.
v2.starko.one/dashboard/analytics
Reporting
72%

Team performance

Per-assignee volume and speed. Issues are attributed to whoever is assigned at the time of closing.

Volume over time per assignee

Ana Kovač Luka Marić Marko Ilić Iva Perić Unassigned
AssigneeTotal issuesResolvedWeb widgetEmailWhatsAppCreated manuallyAPIAvg. touches per issueMedian first responseMedian time to resolutionMedian handle time
AKAna Kovač14113658382015102.19m4h 12m1h 31m
LMLuka Marić1181124832171382.617m6h 05m2h 10m
MIMarko Ilić97934026141072.921m7h 44m2h 38m
IPIva Perić625924179752.312m5h 20m1h 47m
Unassigned29231284321.248m1d 2h·
Pipeline

Sales pipeline from your deal stages

The Sales pipeline block follows the deals created in the selected timeframe through the stages you defined for deals: what is open, what it is likely worth, and what closed.
  • 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.
v2.starko.one/dashboard/analytics
Reporting
72%

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 deals created in this periodCountValue
Lead

24

Qualified

15

Proposal

10

Negotiation

7

Won

5

100%63%42%29%21%
StageIn stage nowReachedFrom previous
Lead10%6€38K24€214K·
Qualified30%4€52K15€168K63%
Proposal60%3€31.5K10€122K67%
Negotiation80%1€14.9K7€86K70%
Won100%5€61K5€61K71%
Widget and knowledge

What customers ask, and what the AI could not answer

The last part of the page is about demand and the Knowledge hub. It shows what customers ask about, which articles the AI relies on, and which questions still have no good 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 in chat

Ask for the number instead of opening the page

Starko AI can query the same reporting layer. Ask ⌘L, the assistant in Slack or an MCP client how last month compares with this one, who has the slowest first response, or which hour is busiest. The same owner and admin permission applies.
  • 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.