Nobody plans to spend their day switching tabs. It just happens: the customer email is open in Missive, the payment question means a jump to Stripe, the order check means a jump to Shopify, and the account note lives somewhere in ClickUp. Each jump takes a few seconds, but a support day is made of hundreds of them. The real cost is not the seconds; it is the attention that never fully returns after each switch. This post walks through how to count those lookups, what context switching does to your focus, and where the hours actually go.
Counting Lookups In A Normal Week
Start by counting, because the number is usually bigger than anyone expects. Take one support session and track every time an agent leaves the current screen to find an answer in another tool. Count the visits, not the time, and keep a rough tally for the day.
Every refund question is a Stripe visit. Every order question is a Shopify visit. Every invoice question is a Bokio or Fortnox visit. Every past conversation is a Missive visit. A single customer question can easily produce four or five tool visits before the reply is written.
Multiply that by the number of tickets in a week. A team answering forty tickets a day with five lookups each is doing a thousand lookups a week, each one a small journey away from the actual work. The count is also a map of where the context actually lives.
Attention Lost To Context Switching
The seconds are the visible part; the attention cost is the hidden part. When a person switches from writing a reply to scanning a Stripe dashboard and back, their focus does not follow instantly. Research on context switching is consistent: each interruption costs more than the interruption itself.
The toll shows up as the wrong number pasted, the reply that repeats something from the previous ticket, and the question that was already answered two screens ago. These are not carelessness. They are the predictable result of a workflow built on jumps, and they cost more to fix than to prevent.
Reducing the jumps reduces the mistakes that come from them. Ziikly collapses the count rather than moving it around: one email search queries every connected tool in parallel, so the five visits become a single profile on one screen, and the attention stays with the customer.
Where The Hours Actually Go
Across a week the tab switching adds up to real hours, and they do not show up in any report. A lookup that takes two minutes across three tabs looks like a small thing, until it happens sixty times a week. Then it stops looking small.
Run the rough math. If the average customer question needs three minutes of tab hopping to gather context, and a support day answers thirty such questions, that is ninety minutes a day spent only on gathering. Before a single reply is written, that time is already gone.
A year of that is hundreds of hours. For a small team, that is the difference between adding a part-time hire and not. The hours come back as better replies and calmer days when the context arrives on one screen. The number worth tracking then is context time per ticket.
Frequently asked questions
How Do I Measure This In My Team?
Track the tool visits needed to gather context for one ticket, multiply by weekly ticket volume, then estimate the minutes. Ziikly removes most of those visits by querying every connected tool in a single email search. The same measurement shows the before and after.
Is tab switching really a big enough cost to fix?
Yes, because the cost multiplies. A two minute lookup repeated sixty times a week is two hours a day of pure context gathering, plus the attention loss each switch causes. Small per switch, but large per week and enormous per year.
Top comments (0)