01
Understand incoming demand
Explore conversation volume over time. Break the work down by company, channel, priority, label, group or team.
Understand the work.
Find the next improvement.
See what is arriving, how your team responds, and where service levels need attention. Put the numbers back in the context of your customers.
Explore the reportsNodeHub AnalyticsIllustrative product walkthrough
A CLEARER PICTURE OF THE WORK
Illustrative reportStart with a better question.
DemandWhat's coming in?
Understand conversation volume.
ResponsivenessHow are we responding?
Explore the time to a first reply.
Service levelsWhere should we focus?
Review service level outcomes.
See the pattern over timeTREND ILLUSTRATION
Earlier in the periodLater in the period
Example shape only. Your reports use your workspace data.
FROM PATTERN TO QUESTION
Put the trend in context.
Use a reporting period to understand changes in the queue, then inspect the work behind them.
Observe. Investigate. Improve.FROM DEMAND TO DETAIL
Better questions. More useful reports.
Use the reporting period and breakdowns that match the question your team is trying to answer.
02
Review responsiveness
Track response and resolution metrics across a selected period. Look for changes before deciding which process to adjust.
03
Inspect service levels
Review met and breached targets, trends and affected tickets. Service-level reporting depends on the policies configured in your workspace.
04
Listen to customer feedback
Review the satisfaction responses customers actually submit. Read them alongside the support activity that prompted them.
05
Choose a useful perspective
Move from the overview to a company, team or channel breakdown. Keep the timeframe consistent while investigating a pattern.
06
Keep reports in context
Reporting uses the selected workspace and business. Access to administrative insights follows your workspace permissions.
THE PRACTICAL DETAILSBefore you
Before you
get started.
Are the numbers in the tour real customer data?
No. Marketing illustrations explain the report layout. The actual Analytics area reads the activity and feedback in your workspace.
Can I see which company is generating the work?
Yes. Reporting includes company breakdowns alongside channels, teams, labels and other dimensions. Available results depend on the data recorded for the selected period.
Does this replace reviewing a workflow run?
Use Analytics for support reporting and workflow run history for step outputs, errors and execution details. They answer different questions about the same operation.
Turn an observation into a better process.
NodeHub Desk
Return to the customer conversation with the context your team needs.
Explore NodeHub DeskSupport operations
Connect recurring requests to a process with clear handoffs and review.
Explore Support operationsThe platform
See how reporting, support and automation fit together.
Explore The platform