The report

This is the basic report. Run the simulation to get one for your own team.

Below is the generic version, on invented numbers: where the hours go, whether enough people are online when the work arrives, and what people log versus what OLi measured. Answer five questions about your team and we run the same analysis against your size, mix and channels — a longer, specific report, in about a minute.

What you get

The basic report.

Illustrative — synthetic data

Illustrative · synthetic data

Measured occupancy per agent, against an 80% target

40%team occupancy. No agent reaches 80%; 12 of 24 are below 40%.

Agent 11: 60% measured occupancyAgent 12: 55% measured occupancyAgent 10: 55% measured occupancyAgent 14: 53% measured occupancyAgent 18 (lead): 53% measured occupancyAgent 13: 52% measured occupancyAgent 22: 49% measured occupancyAgent 16: 49% measured occupancyAgent 09: 49% measured occupancyAgent 15: 47% measured occupancyAgent 24: 46% measured occupancyAgent 04: 44% measured occupancyAgent 23: 39% measured occupancyAgent 19: 37% measured occupancyAgent 06: 35% measured occupancyAgent 20: 34% measured occupancyAgent 01: 33% measured occupancyAgent 21: 32% measured occupancyAgent 02: 31% measured occupancyAgent 08: 28% measured occupancyAgent 05: 22% measured occupancyAgent 03: 20% measured occupancyAgent 07 (lead): 19% measured occupancyAgent 17: 17% measured occupancy
AgentTeam lead80% target
Run this for your team →

Illustrative · synthetic data

AI use cases and automations, ranked by measured hours

2,250–3,100 hsavable a month across eight use cases, from 21,584 measured hours.

  • Ticketing ↔ industry-specific platform lookups2,420 h · 485–725
  • Bank reconciliation1,450 h · 290–430
  • Ticket reply drafting1,380 h · 415–550
  • Call wrap-up & notes1,370 h · 340–480
  • General-ledger transaction entry1,090 h · 380–545
Measured hours / monthSavable (moderate)
68%of staff (108 of 160) pasted work into a public AI chatbot. Shadow AI, ungoverned.Run this for your team →

Illustrative · synthetic data

People online vs work arriving, by hour of day (ET)

5.5agents online in a typical hour; the work arriving keeps only 1.8 of them busy.

00:00 ET — 4.9 agents online, 0.7 busy01:00 ET — 5.0 agents online, 0.5 busy02:00 ET — 4.8 agents online, 0.4 busy03:00 ET — 4.9 agents online, 0.4 busy04:00 ET — 6.1 agents online, 0.4 busy05:00 ET — 6.1 agents online, 0.6 busy06:00 ET — 5.5 agents online, 0.8 busy07:00 ET — 5.6 agents online, 1.2 busy08:00 ET — 6.7 agents online, 1.7 busy09:00 ET — 6.2 agents online, 2.2 busy10:00 ET — 6.2 agents online, 2.7 busy11:00 ET — 6.8 agents online, 3.0 busy12:00 ET — 6.8 agents online, 2.9 busy13:00 ET — 5.6 agents online, 2.5 busy14:00 ET — 4.9 agents online, 2.0 busy15:00 ET — 5.0 agents online, 1.9 busy16:00 ET — 4.8 agents online, 1.9 busy17:00 ET — 4.4 agents online, 2.1 busy18:00 ET — 4.9 agents online, 2.8 busy19:00 ET — 5.5 agents online, 3.4 busy20:00 ET — 5.6 agents online, 3.7 busy21:00 ET — 6.1 agents online, 3.1 busy22:00 ET — 5.6 agents online, 2.1 busy23:00 ET — 4.9 agents online, 1.3 busy00061218
Agents onlineAgents busy with arriving work
Run this for your team →

Illustrative · synthetic data

Handle time: what agents log vs what OLi measured

7agents log under 3 min per case and 3 log over 15 min. Measured at the desktop: about 7.9 min.

Agent 22: logged 1 min, measured 8.8 minAgent 02: logged 0.9 min, measured 7.5 minAgent 24: logged 0.8 min, measured 7.2 minAgent 15: logged 0.9 min, measured 7.1 minAgent 10: logged 2.3 min, measured 8.3 minAgent 06: logged 2.2 min, measured 7.9 minAgent 20: logged 2.3 min, measured 7.5 minAgent 18: logged 7.9 min, measured 8.9 minAgent 07: logged 7.2 min, measured 8.1 minAgent 01: logged 8.1 min, measured 8.8 minAgent 03: logged 6.6 min, measured 7.3 minAgent 05: logged 6.8 min, measured 6.9 minAgent 19: logged 7 min, measured 7.1 minAgent 14: logged 9.2 min, measured 9.3 minAgent 21: logged 6.9 min, measured 6.8 minAgent 11: logged 8.5 min, measured 8 minAgent 16: logged 9.6 min, measured 8.9 minAgent 08: logged 9.1 min, measured 8.3 minAgent 12: logged 9.8 min, measured 9 minAgent 09: logged 7.9 min, measured 7 minAgent 23: logged 9.1 min, measured 8.1 minAgent 04: logged 17.8 min, measured 8.9 minAgent 13: logged 15.8 min, measured 6.7 minAgent 17: logged 17.7 min, measured 8 min

0–20 min per case, one column per agent

Measured at the desktopSelf-logged in the tracker
Run this for your team →

Invented organizations, synthetic numbers — the shape of the findings, not a real customer’s. Answer five questions and we run the same charts against your team’s size and mix. Run the simulation for your team →

Run the simulation for your team.

Answer five questions about your team and tell us where to send the report. You get a fuller report than the one above: the hours an assessment would measure at your size, a planning range for how many of those hours are recoverable, what your mix suggests we would find, which assessment fits — and a plain statement of what a simulation cannot know. Work email only.

50% customer-facing50% back office

How does the work arrive?

If clients pay for hours, efficiency can cut revenue — the report handles that differently.

Optional: loaded cost per person, to see the range in dollars

Your report opens straight away, and we email you the link. Work email only. No attachment, no call unless you ask.