Contact-minutes reveal front-desk workload that ticket counts hide

Published November 4, 2026

The ticket count that treats every contact as equal

A front desk closes forty tickets in a day. Another desk closes twenty-five. The first looks busier, and a report may treat it that way. But one desk may have answered forty password resets, while the other spent the same hours on billing disputes, schedule changes, and a facility issue that required three callbacks.

Ticket counts measure activity, not workload. They are easy to export and easy to compare, which is why they spread. They also reward the wrong behavior: splitting one hard conversation into four tickets looks productive, and spending twenty minutes resolving a member's problem in one contact looks slow.

This note describes a workload review a fitness virtual assistant can prepare for a studio manager. It does not propose a staffing formula or an industry standard. It proposes a way to measure contact-minutes, separate waiting from handling, and compare channels and shifts without turning the result into a ranking of people.

Define a contact-minute before collecting data

A contact-minute is one minute of staff attention spent on a member or internal contact. It begins when the staff member starts working the contact and ends when the staff member stops. It does not include time spent waiting for the member to reply, and it does not include time spent on unrelated tasks between messages.

The definition needs boundaries. If a staff member reads an email, checks a schedule, and replies, the handling time is the total attention spent, not just the typing time. If a call is placed on hold while the staff member checks a roster, the hold time is part of the contact because the staff member is still responsible for it. If a contact is handed to a manager, record the handoff time and start a new segment under the manager.

Decide whether follow-up contacts count as one case or several. A member who calls three times about the same issue is one case with three contacts. A member who asks about a class and then asks about a membership freeze is two cases. The distinction matters because workload is driven by cases, while queue volume is driven by contacts.

Write the definition in one paragraph and keep it with the report. If the studio changes the definition, mark the change date. A trend line built on two different definitions is not a trend; it is two unrelated measurements placed next to each other.

Build the log from timestamps the studio already has

Most studios do not need a new time-tracking tool. Phone systems record call duration. Chat and text platforms record message timestamps. Email records thread times. The booking platform records when a member was checked in or a schedule change was made. The review can combine these sources without asking staff to start a stopwatch.

Start with one channel and one week. Pull the contact identifier, the channel, the start time, the end time, the staff member or role, and the outcome. For written channels, use the first outbound reply and the last outbound reply in the thread as the handling window, then subtract long gaps that clearly represent waiting for the member. State the subtraction rule.

Do not pretend the timestamps are exact. A chat window may include a staff member switching to another task. A call log may round to the nearest minute. The report should describe the source and the rounding rather than presenting a precision the data does not support.

If the studio uses a shared inbox, assign each contact to the person who actually handled it. A queue that is visible to five people but worked by one should not be divided evenly across five. The assignment can be approximate, but it should be recorded and reviewed.

Separate waiting time from handling time

Waiting time and handling time answer different questions. Waiting time tells the studio how long a member stood at the desk or sat on hold. Handling time tells the studio how much staff attention the contact consumed. A short call with a long hold can feel slow to the member and still be cheap in staff minutes. A long call with no hold can feel fast and consume a large share of the shift.

Record both when the data allows. For phone contacts, the call system may provide queue time and talk time separately. For walk-ins, the check-in timestamp and the start of service give an approximation. For written channels, the time to first reply is the waiting measure, and the active handling window is the workload measure.

Do not add waiting time to handling time and call the result workload. The member's wait is not staff attention. Combining the two inflates the workload figure and makes a queue problem look like a staffing problem. Keep them side by side and interpret them together.

The distinction is especially important during class changes. A front desk may have a long walk-in queue and very short handling times because most questions are simple. Adding staff may shorten the wait, but it may not change the total contact-minutes much. The decision depends on which number the studio is trying to move.

Compare workload across channels and shifts

A channel comparison should use the same definition and the same window. Report the number of contacts, the total contact-minutes, the median handling time, and the share of contacts that required a handoff. The median is often more useful than the average because one long dispute can pull the average away from the typical contact.

Compare shifts with context. A morning shift may handle more check-ins and fewer billing questions. An evening shift may handle more schedule changes and parent inquiries. The mix explains the difference as much as the volume does. A report that compares only totals will imply that one shift is slower without showing why.

Normalize carefully. Contact-minutes per staffed hour is a reasonable measure because it accounts for the length of the shift. Contact-minutes per contact is useful for understanding complexity. Neither one is a productivity score. A high number can mean a busy desk or an understaffed one, and a low number can mean a quiet desk or a desk that is closing tickets without resolving them.

Include internal contacts if the front desk handles them. A staff member who spends an hour coordinating a trainer substitution is working, even if no member contacted the desk. The review should say whether internal work is in scope. Excluding it makes the front desk look less busy than it is and pushes the work out of the staffing conversation.

Use the result to staff a shift, not to rank people

The purpose of the review is to decide where attention is needed. If contact-minutes cluster at the start and end of a shift, the studio may need overlap coverage rather than more total hours. If one channel consumes a large share of handling time, the studio may need a template, a self-service option, or a clearer routing rule.

Look for contacts that could be prevented. A password reset that takes eight minutes because the member cannot find the app is a candidate for a short guide. A schedule question that requires three internal checks is a candidate for a better roster view. Preventing a contact is usually better than handling it faster, provided the member still gets a clear answer.

Do not use the numbers to compare individual staff without accounting for mix. Two people with the same contact-minutes may have handled very different work. If the studio wants to discuss individual performance, use case quality, resolution, and member feedback alongside workload. Contact-minutes alone cannot distinguish a difficult caseload from a slow worker.

The assistant can prepare the report and flag the largest sources of contact-minutes. The manager decides whether to change staffing, routing, or policy. A report that arrives with a recommended schedule but no authority behind it will be treated as an opinion, not a finding.

Limits and sources

This note is a local workload method, not a claim about typical front-desk staffing. The U.S. Bureau of Labor Statistics publishes occupational information for fitness trainers and instructors, which provides context for the workforce but does not define front-desk contact-minutes. The Small Business Administration offers general guidance on managing business records, which supports the documentation discipline described here but does not prescribe a staffing measure. The NIST Privacy Framework informs how to limit the contact data used in the review. The U.S. Department of Labor's Wage and Hour Division publishes guidance on hours worked and recordkeeping, which is relevant when staff time is recorded, but it does not define this metric.

Use the method as a local protocol. Adapt the channels to the studio's systems, write down the definition and the rounding rules, and keep the source exports with the report. A defensible workload figure is one that a manager can rebuild from the same records after a change in staff or software. A figure that cannot be rebuilt is a conversation starter, not a staffing decision.