Workforce management

Time tracking that knows the difference between clocked in and working

A generic time clock records that someone started their day. OpsyncHub records what they did in it — because the timer and the dialer are the same system.

Request access See pricing
app.opsynchub.com/time-tracking

Today · Collections floor

12 on shift
J. Mercer 7h 48m
Active 71%Idle 12% Break 17%
A. Ndiaye 8h 02m
Active 78%Idle 8% Break 14%
R. CastilloReview · 47 7h 55m
Active 34%Idle 52% Break 14%

Idle is derived — total minus break minus active — so it cannot be absorbed into "hours worked".

What actually gets measured

Most time tracking bolted onto a CRM records a start and a stop. These are separate stored values on every session.

Clocked time, split four ways

Every session records total, active, break and idle minutes separately. Idle is derived — total minus break minus active — so it cannot be quietly absorbed into "hours worked".

Active time means product activity

Active minutes come from the activity log: calls, records touched, dispositions set. A session with a clock running and nothing happening in the product reads as idle, because that is what it was.

Breaks are typed, not guessed

Short, lunch and personal are separate break types with their own start, end and duration. Break minutes never count as active time, and never silently inflate idle either.

Attributed to a campaign

Sessions carry a campaign, so hours land against the work they were spent on rather than a single undifferentiated timesheet.

Shifts, in the agent’s own timezone

  • Shifts are set per agent per day of week, with a start and end time.
  • Each schedule carries its own timezone — a distributed team is not forced onto one office clock.
  • Sessions left running are closed by a scheduled auto-clock-out job rather than accruing overnight.
  • Timesheets are available by day, week and current status, plus a live view of who is on shift.

Idle detection is off until you turn it on

Input monitoring requires employee disclosure in many jurisdictions. So it ships disabled, and it is a per-organization setting an admin has to switch on deliberately — not a default applied quietly to every tenant.

When enabled

Sessions are scored 0–100 over a trailing window, and the score comes with the reasons that produced it rather than a bare number. Amber and red thresholds default to 30 and 60 and are configurable per organization.

Clocked in over an hour with under one product action per hour
Fewer than three actions per hour — possibly idle
Mouse activity with no keyboard input — the mouse-jiggler signature
An unusually high mouse-to-keyboard ratio — possible automation

A flag is a prompt to look, not a verdict. The score surfaces which sessions are worth a conversation; it does not decide anything on its own.

What this is not

OpsyncHub is workforce management for phone teams. It is not an HRIS, and it does not pretend to be one.

There is no PTO or leave management, no benefits administration, no employee document or tax-form storage, and no performance-review cycle. If you need those, you need an HR platform alongside this, and we would rather say so now than after you have bought.

What it does own is the loop that generic tools break in half: the hours an agent worked, the work they did in those hours, and what they get paid for it.

Ready to replace
your entire ops stack?

Get access

Request access · Onboarding done for you