Time tracking for customer support: how much of a shift is the help desk

2 October 2026 · 6 min read

On a support shift, the help desk is where the work gets counted, but it is rarely where all of the work happens. Answers get found in internal docs, confirmed in team chat, followed up by mail and talked through on calls, and none of those minutes appear in a ticket report. A week of your own per-app record on the Mac shows the real split, and if your help desk runs in Chrome, Brave, Edge or Vivaldi, an itemized record can pull it out of the browser line so you see its share of the shift directly.

Where a support shift goes

Most help desks report on tickets: how many you closed, how quickly you replied, how the customer rated it. Useful numbers, but they describe the queue, not your shift. A ticket that took forty minutes to resolve might have had six minutes of you typing in the help desk, with the rest spent somewhere else:

• Internal docs and the knowledge base, looking for the article that covers the edge case.
• Team chat, asking engineering whether the bug is known, or a senior colleague whether the refund is allowed.
• The product itself, an admin console or a test account where you reproduce what the customer saw.
• Mail, for the customers and partners who never use the portal.
• A call app, for the conversation that was faster than three more replies.
• A spreadsheet, for the known-bugs list or the shift handover.

None of this is wasted; it is how a good answer gets made. But unmeasured, it makes a shift look as though it should have closed more tickets, and the work around each ticket stays invisible, including to you.

Measuring your own split for a week

Pick an ordinary week: not a launch, not the week of an outage. Then:

1. Start a per-app record. Punchcard sits in the menu bar, notices which app is in front, and at the closing time you set prints a receipt of the day: the top five lines with the time on each, everything else as MISC, and a total. Set the closing time to the end of your shift. Out of the box it records app names only, never window titles, page titles or anything on screen, and it needs no macOS permissions.
2. If the help desk lives in Chrome, Brave, Edge or Vivaldi, switch on itemizing. In Punchcard’s Settings, turn on “Itemize websites”. The first time, macOS asks once per browser, in the form “Punchcard wants access to control Google Chrome”. After that, browser time prints as the sites you used. The help desk gets a line of its own: under its name if Punchcard recognizes the site, or as its bare site name with a globe if not. The internal wiki and the admin console get lines too if they are separate sites, competing with your apps for the top five; anything that misses the cut lands in MISC.
3. If you use Safari, Firefox or Arc, the browser stays one line. Punchcard does not itemize those browsers. In Safari on macOS Sonoma or later, the workaround is to turn the help desk into its own web app with File, Add to Dock, so it gets a line of its own; web apps vs desktop apps covers what that does to the record.
4. Write one line per shift. “Busy queue, two escalations”, or “quiet, drafted a help article”. The receipt gives the minutes; the line explains them.
5. Read the week together. The Sunday week roll puts the whole week on one strip.

Tracking never expires, the CSV export works without a license, and the first two receipts are free; printing after that is a $9 one-time license. The CSV has one row per session, with the site when itemizing is on, so you can total a week from it without printing anything.

Reading a support receipt

Start with the help desk line, but the shape around it says more.

The help desk is the longest line by a distance. A queue-heavy shift where most answers came from memory or saved replies. If every shift looks like this, the off-queue work you are asked to do (help articles, bug write-ups, training notes) has nowhere to happen.

Chat, docs and the admin console together rival the help desk. Much of the shift went into building answers rather than sending them. That can mean hard tickets. It can also mean the knowledge base does not answer the questions customers actually ask.

MISC is large. Everything outside the top five lands there, so a big MISC means the shift was spread across many apps and sites, none for long. This is the receipt’s view of tool-hopping.

The call app line is shorter than your calendar says. A record of the app in front counts a call as whatever you were looking at. If the ticket was in front while you talked, the call lands on the ticket’s line, which is arguably where it belongs.

Some limits before you draw conclusions. A chat window on a second display that you glance at adds nothing to the chat line; only the front app counts. Sites you spent under a minute on stay on the browser’s own line. If the internal docs live on the same site as the help desk, they share its line, because Punchcard keeps the site name and never the path. Private windows are never read, so time in them stays on the browser line too.

What it is not

Punchcard is a personal record for the person at the Mac. It does not count tickets, measure reply time or handle time, or know which customer you were helping. It has no team features, no shared dashboard and no manager view. Tracked data stays in one file on your Mac. Because it never keeps a full address, a ticket number in the URL is never recorded, and page titles, where customer names often appear, are never read.

If your company runs monitoring software, that is a separate tool with a separate purpose; what monitoring software sees and a personal tracker should not sets out the difference. On a company-managed Mac, check the software policy before installing anything.

Using the number to ask for focus time

Support teams are often asked to write help articles, improve saved replies or document bugs “when the queue is quiet”. The queue is rarely quiet for long enough. Two weeks of receipts turn that into something you can show.

Bring the pattern, not a complaint: “Over the last ten shifts, the help desk and chat took nearly the whole day, and docs work shows up on two of them.” Then make one specific request, such as a block off the queue twice a week at the hour when volume is lowest. During that block, a Focus (System Settings, Focus) can silence notifications from the apps you are stepping away from. Measure the next two weeks the same way and see whether the docs line appears.

Using the number to cut tool-hopping

If the same three lines sit just under the help desk every day (chat, the internal wiki and the admin console, say), each ticket is probably making a round trip through all three. A receipt shows the spread, not the number of switches; the real cost of switching apps all day has a paper tally that counts those. The spread is still enough to ask useful questions:

• If the wiki line is large, which articles do you open every day? Turning the top few into saved replies or internal notes keeps the answer inside the help desk.
• If chat with engineering is large, would a short form for known-bug checks save both sides a thread?
• If the admin console is large, does every issue need reproducing, or only certain kinds?

Change one thing, measure a week, and compare the receipts.

Questions

Can my team lead see my receipts? Not unless you send them. A receipt exports as a 1080x1350 PNG or plain text if you choose to share it, showing app and site names with minutes. There is no account, no cloud and no team view, and the only network use is the license check.

Does Punchcard count tickets or reply times? No. It measures time in front, by app and, if you switch itemizing on, by site. Ticket counts and reply times come from your help desk’s own reports.

Our help desk runs in Safari. Can Punchcard split it out? Not by site. Safari’s scripting cannot tell a Private window from a normal one, so Punchcard leaves Safari as one line. On macOS Sonoma or later, turning the help desk into a web app with Safari’s File, Add to Dock gives it a line of its own.

Will a ticket page put a customer’s name on my receipt? No. Punchcard keeps only the site name, never the full address, the page title or anything on the page.