Skip to main content

​
What Analytics shows

Analytics → Dashboard brings request handling and automation outcomes into one view. Open Analytics from the left sidebar. Your organization and team roles determine the data you can read. The Dashboard uses one reporting period and team scope for every card. The existing Opportunities page is separate; Dashboard filters do not change its scope or records.

​
Read operations metrics

1

Open Analytics → Dashboard.

2

Choose the reporting period.

Open the calendar button. Select Last 30 days, This quarter, or Since launch, or choose dates in the calendar. Custom dates include both selected days and use UTC. A custom period can span up to 365 days.
3

Choose the team scope.

All teams includes the active teams you can read. My team uses your current team. Use the team selector to choose one authorized team. Organization administrators can also select Unassigned.
4

Read the summary and metric cards.

The top-left summary uses the current report values. It is not a generated recommendation. Use Refresh beside the team and period selectors to load the same period and scope again.

​
Dashboard metrics

A request item is a ticket or a requester conversation that had not produced a counted ticket by report end. A later ticket does not remove an earlier conversation from its reported period. Channel chart titles show the channel name, request count, and share. Titles use request for a count of one and requests for other counts. Comparisons use the immediately preceding period of equal length. Since launch starts at organization creation and has no comparison. Percentage-rate changes use percentage points. Human resolution changes use duration; a shorter duration is favorable.

​
Read the numbers together

These examples use made-up numbers for one reporting period and team. AI deflection includes both tickets resolved by Flow and conversations that Flow completes without creating a ticket. A successful automation run and a resolved request measure different outcomes. A run can finish one part of a request while a person still has work to do. Use How Flow shares the load to see who resolved requests, then inspect individual runs in Monitoring.

​
Understand data limits

- means a rate has no observations, a duration has no resolved sample, or a metric lacks supported evidence. It does not mean zero. Empty periods show zero counts while unavailable rates show -. Conversations without tickets use outcome labels for resolution. Older ticket outcomes or knowledge answers may lack retained evidence, so those counts can be incomplete. Historical connected discoveries can lack the team recorded at discovery. Team-scoped totals exclude those discoveries instead of guessing from current asset ownership. Organization-wide administrator totals can include them. Creating an asset manually does not record a connected discovery. The helpfulness buttons select a local response; they do not save feedback.