All articles
IT support

Twelve fixes before 11am, twenty before the end of lunch: a morning in James's inbox.

Published10 September 2026
Reading time4 min read
AuthorJames Powell
In short

By 11am on one ordinary Thursday, James had already run twelve on-demand remote support sessions. By the end of lunch that had climbed to twenty, peaking at six sessions in the busiest hour. Nothing in that stretch was scheduled or planned around, it was simply what came in. By early afternoon it had tapered away to nothing. That's not a busy outlier for us, that's a fairly normal morning.

Thu 10 Sep 2026 · before lunch The morning in numbers
  1. 12 Sessions before 11am

    Before most offices are through their first coffee

  2. 20 Sessions before end of lunch

    On-demand remote fixes, back to back

  3. 6 Busiest hour

    The most sessions handled in any single hour

  4. 4 Average per hour

    Across the whole morning stretch

One engineer, one ordinary Thursday morning.

One ordinary Thursday morning

No client is going to remember exactly which morning this was. That's rather the point. There was no big incident, no outage, nothing that would make it onto a status page anywhere. Just the ordinary background hum of small IT problems that stop someone getting on with their day, one after another, each one landing on James's desk and getting picked up.

By 11am, twelve of those problems had already been resolved remotely. By the end of lunch, that had climbed to twenty.

Twelve before 11am, twenty before lunch

The shape of the morning matters as much as the total. Activity built steadily from early morning, with twelve sessions already done and dusted before 11am, before most offices are through their first coffee. From there it kept climbing through a genuinely busy stretch where the busiest single hour saw six separate sessions come through, taking the running total to twenty by the end of lunch, before easing off again into the afternoon. Across the whole stretch that averaged out at four sessions an hour.

It wasn't spread evenly and it wasn't one long flat queue either. It rose, it peaked, and it tapered, the way real demand actually behaves rather than the way a spreadsheet would tidy it into.

A morning that builds, then stops

What the numbers don't show is which client each session belonged to or how long any one of them took. What they do show clearly is the rhythm: a sharp rise once the working day gets going, a sustained busy patch through mid-morning, and then a steady fall away to nothing at all by the afternoon. There's no repeat of that pattern later in the day, once it tapers off, it stays off.

Six sessions in the busiest hour, one in the quietest, and nothing at all by mid-afternoon. That's not a spike, that's an ordinary Thursday morning.

That rhythm is the useful bit. It tells us support demand isn't a trickle that could, in theory, be handled by whoever's free. It's a proper morning's work, concentrated, that needs someone dedicated to picking it up as it lands.

And that's still just one morning

Twelve sessions before 11am, twenty before the end of lunch, one engineer. That's James on his own, on one ordinary Thursday, and it doesn't include whatever comes in over the rest of the afternoon, or what the rest of the team picked up at the same time.

What this looks like over a normal month

It's worth being honest about what we actually know here versus what's a reasonable estimate. We know, precisely, what one engineer got through in one morning on one Thursday: twelve sessions before 11am, twenty before the end of lunch, peaking at six in the busiest hour. What we don't know from that alone is whether every morning looks exactly like this one.

But we don't need to guess blind. Our own reporting shows support demand follows a clear weekly rhythm, busy through the working week, dropping away hard at weekends, rather than being spread evenly across every day. So a reasonable, conservative way to translate one morning into a month is to assume mornings like this one are typical of a working day, and then count only the working days: roughly 22 in a normal month, once weekends are taken out.

Twenty sessions by the end of lunch, across around 22 working days, comes out at somewhere in the region of 440 sessions a month, for one engineer, before the afternoon even starts. That figure doesn't include anything picked up after lunch, and it doesn't include a single session from the rest of the team. It's a floor, not a ceiling, and it's built from a real morning's numbers rather than a guess plucked from nowhere, but it's still an estimate, not a reported total, and worth treating as one.

Scale that up across the full team, for the full working day, for a full month, and the number stops being one anyone would want to put on a rate card. That's rather the point of leaving it there.

Related reading: which keyboard shortcuts are worth learning.

Wondering what your own morning would look like on our side?

If you're curious how quickly a real problem on your own systems would actually get picked up, rather than how quickly a contract says it should, we're happy to talk it through.

Get in touch