PRACTICAL GUIDES

Practical guides for service desks and internal support teams

If the work never gets counted, it never makes it into the plan. These guides cover the support activity ticket reports may miss, the assumptions behind capacity planning, and a low-friction way to account for walk-up demand.

Practical guidance from IT-Service KühnePublished August 23, 2026

CHOOSE THE PROBLEM YOU NEED TO SOLVE

One subject per guide. No catch-all article.

01 · VISIBILITY

Track IT support workload beyond ticket counts

Quick questions, equipment handoffs and unplanned assistance may never appear in your ticket reporting.

What you will learn
How ticket counts, time tracking and category-based activity capture differ.
Who it is for
Support leads who need a broader workload picture without requiring minute-by-minute tracking.
Account for work the queue may miss →
02 · CAPACITY

Service desk workload and capacity planning

Activity volume does not tell you whether the team has enough workable capacity.

What you will learn
How volumes, standard minutes, productive hours and a target utilization assumption fit together.
Who it is for
IT leaders and service desk managers who need a transparent planning model with honest limits.
Turn activity counts into a planning view →
03 · WALK-UP

Track walk-up IT support

Face-to-face visits should be visible without forcing every brief exchange through a full ticket workflow.

What you will learn
When a ticket is required and when a quick categorized count may be enough.
Who it is for
Teams running a tech bar, support counter, help desk window or other in-person channel.
Build a sensible walk-up capture rule →

MISSING WORK CREATES MISSING CONTEXT

Ticket data is useful. It is not every kind of work.

A ticketing platform should remain the system of record for incidents, requests, ownership, approvals and service commitments. Category-based activity capture answers a narrower question: what short, repeatable work is the team handling outside that formal path?

The guides show how to collect a planning signal without pretending it is exact labor time or a guaranteed staffing answer.

CountPilot touch interface for recording recurring service activities
A large touch interface keeps routine activity capture brief.

WHERE COUNTPILOT FITS

A lightweight capture layer, not an ITSM replacement.

CountPilot records recurring activity through configurable touch buttons. Standard minutes turn counts into estimated workload and planning values. General mode works without assigning activities to named employees; an optional employee mode is available where the organization has a justified use for it.