Reporting: tickets, conversations and sales

Reporting answers how support and product work is going: how many tickets, how fast, by whom, and what customers are asking. Open Reporting from the sidebar (it needs the analytics capability, which owners and admins have by default).

reporting tickets

Controls

Tickets and Conversations switch the subject.

The period picker offers presets and a custom range; Day, Week and Month set the granularity of charts.

Sources, tags and assignees filter everything on the page.

Tickets

Client funnel: visitors who interacted, who identified themselves, and the conversion between the steps.

Sales pipeline: deals created in the period, open and weighted value, won value, win rate, average deal size and cycle.

Tickets over time: created and closed per day, week or month, with the backlog line.

Time in status: how long tickets spend in each status group, which shows where work waits.

By assignee, team, tag and priority: volume and resolution time per segment.

SLA: first-response and resolution attainment and breaches.

Starko AI: runs, pull requests merged and tickets closed by the agent.

Conversations

reporting conversations

Volume by channel and by hour of day.

Handled by the assistant versus handed to a person, and the hand-off reasons.

Response and resolution times for human replies.

Sentiment over time from conversation summaries.

Top topics and the ones that most often lead to tickets.

Exporting

Every chart has a menu to download its data as a spreadsheet. Ask Starko (⌘L) can also answer reporting questions in chat: "how many tickets did we close last week, by assignee".

Related pages

Settings → Usage and Settings → Fix agent cover Starko AI cost and outcomes.

Improvements → Statistics covers what Starko AI proposed from visitor sessions.

Did this answer your question?