Five years of team-level visibility across three countries

The need

The operation runs customer support for a technology company from several sites, each with its own supervisors, shift patterns and local rules on workplace monitoring. The question operations wanted answered was the one every contact center has: how is agent time distributed across the tools of the job, by team, and how does that change when something changes.

Three constraints shaped the choice. Data minimization, because the sites' local rules on workplace monitoring favor it: no keystroke capture, nothing outside working hours and personal browsing counted without a name. Silent deployment on managed Windows fleets by the customer's own IT, with no user interaction. And a supervisor view limited to the supervisor's own teams.

The setup

The customer runs on a dedicated backend, separate from the application that serves other organizations, and on its own update channel, so a client update reaches its machines when its IT has said so. Installation is silent through the customer's deployment tooling, and each PC signs in with its Windows account; nobody types a ReclaimTime password.

A corporate list defines the applications and sites that count as work. Time in those is recorded under the agent's name. Everything else is counted anonymously at group level. Working hours are configured per site, and nothing is recorded outside them.

What it is used for

• •Supervisors review their own groups' time distribution: which tools, how much, week on week.
• •Program managers compare the same program across sites on per-head weekly totals.
• •IT tracks client versions per site from the Versions page and schedules updates on the dedicated channel.
• •Data is exported to CSV for the operation's own reporting.

Why it has lasted

The deployment has run for more than five years. What has kept it in place is unglamorous: it installs and updates without tickets, the data model has not had to be renegotiated with the sites, and the dedicated backend means the customer's data and update cadence are its own.