Hubz.

Reports / Support reports

Support reporting: tickets, targets and satisfaction

Assess ticket status, resolution targets, survey scores and unresolved feedback together.

PRODUCT VIEW

See how it works.

The support quality report assesses ticket resolution and recorded service targets alongside actual survey responses. Overdue open tickets, answered survey scores and experiences reported unresolved are different facts. By separating ticket counts from feedback, the preset report helps identify topics needing follow-up. Scores come from submitted surveys; unanswered surveys remain separate, and the required data sources must be enabled.

Hubz.Workspace / Support reportsDK
EXPLORE THE PRODUCT

Support reports

Sample view
Ticket resolution view24Sample data
Survey and score context12Sample data
Delays and follow-up8Sample data
Support reportsSample period
1
2
3
4
5
6
7
8
9
10
11
12
Values are illustrative product examples, not actual results or performance claims.
01Choose the question and period
02Read the summary alongside records
03Prepare a shareable view
Interface illustration using sample data. The layout is simplified to explain the relevant feature.

FROM NEED TO OUTCOME

Where this helps.

A ticket closed by the team may still be unresolved for the customer. Closure counts or a single average score can hide this distinction and overdue work.

WHAT YOU CAN WORK TOWARDS

Read ticket and survey signals through their own evidence to decide which customer needs contact or which open issue needs priority.

STEP BY STEP

How to use it.

  1. 01

    Choose the question and period

    Select the relevant preset report and date range. Check that your plan enables the required source, and avoid comparing similar-looking totals from different periods.

  2. 02

    Read the summary alongside records

    Read the indicators, charts and rows together. Check which records are loaded and any warnings about incomplete data before drawing conclusions about the whole organization.

  3. 03

    Prepare a shareable view

    Export the relevant table to CSV or save the report view. With a suitable sender configured, choose manual, daily, weekly or monthly delivery and track the result of scheduled sending separately.

INSIDE THE MODULE

What can you do?

FOCUS 01⊙
Support reports
Sample period / records included

Ticket resolution view

Assess open and concluded support work through existing status records and track recorded target times.

FOCUS 02▤
Support reports
Sample period / records included

Survey and score context

Review actually answered surveys, scores and resolution responses. An absent response is not a positive result.

FOCUS 03↗
Support reports
Sample period / records included

Delays and follow-up

Connect overdue targets or unresolved feedback to the relevant ticket to discuss the team's next action.

FOCUS 04◇
Support reports
Sample period / records included

Saved views and delivery schedules

Save the report’s name, type, date range and supported settings. Set delivery days and a time if needed, so you do not have to recreate the view each time.

FOCUS 05⌁
Support reports
Sample period / records included

Tables and CSV

The on-screen table is paginated; CSV includes the rows loaded into the current report. On-screen amounts are formatted for reading; exported values are provided for further analysis.

IN EVERYDAY WORK

What it looks like in practice.

Business support manager

Weekly reports show closed tickets, yet some customers report that their problems continue.

Review status together with feedback rather than judging outcomes from closure counts alone.

Scenarios are illustrative; they are not customer testimonials or measured performance claims.

KNOW WHAT IS INCLUDED

Plans, permissions and limits.

Existing preset report areas are included in every plan. Each type requires its source modules to be enabled and the user to have access to the relevant workspace.

  • This screen is not a general-purpose custom report builder. It uses existing report types and supported settings.
  • CSV exports and indicators are limited to the records loaded into that report. Where a scope warning appears, do not interpret the result as all of the organization's data.
  • The current support_quality type requires both support and quality sources. Its data and export are unavailable when quality is disabled.
  • Tracking target times in a report does not itself establish a contractual SLA guarantee.
Compare plans

YOUR QUESTIONS

About this feature.

01Does access to Reports reveal all data?

No. Reports only use source modules you can access. Quote reporting requires the quote module; marketing reporting requires campaign access.

02Does saving a report send it automatically?

A saved view and a delivery schedule are separate settings. Sending frequency and recipients must be selected, and the background process and authorized sender configuration must be operational.

RELATED WORKFLOW GUIDES

You may also need these features.

DashboardReview sales, risk, support, operations and customer indicators in clearly organized dashboard sections.Sales reportsReview won sales, pipeline, recurring revenue and quote reports alongside the relevant commercial records.Outreach and campaign reportsAssess email campaign results and event preparation through their respective data sources.

MODULES THAT WORK TOGETHER

Explore related modules.

01

Tasks and Kanban

Organize work in lists and Kanban views, keeping customer follow-up visible with an owner and date.

02

Reports and visibility

Review sales, customer relationships, support, operations and data quality through your existing records.

03

Customer support

Manage support as a continuation of the customer relationship, adding knowledge-base, satisfaction and reward records with Business.