Tamper-resistant time clock
One-click or auto clock-in, configurable break types, and offline-buffered punches signed to a device and identity. Disputes get a clean approve/reject trail.
WorkPulse turns clock-in punches into verifiable worked time. Measure active vs. idle minutes, keep agents active through live calls, and give everyone a clear view of their own data — without stealth surveillance.
Consent-first · transparent agent · call-state aware
One Windows agent, one dashboard. Accurate attendance plus the activity signals that explain where the shift actually went.
One-click or auto clock-in, configurable break types, and offline-buffered punches signed to a device and identity. Disputes get a clean approve/reject trail.
Input presence becomes work states. When an agent is on a live call hands-off-keyboard, call-state keeps them active instead of falsely idle.
Foreground app and domain map to Productive / Neutral / Unproductive per team. Window titles and URLs are maskable; sensitive categories are dropped before they leave the device.
A real-time roster of who's working, idle, away, or on break — with threshold alerts for long idle and late or missed clock-ins, pushed to the dashboard, email, or Teams.
Every minute of a shift resolves to one state. The same colors run through the dashboard and the agent's own app, so there's one shared language for worked time — no hidden scoring.
Employee monitoring lives or dies on trust and compliance. WorkPulse is built so customers can defend it under GDPR, the Israeli Protection of Privacy Law, and US state notice rules — and so agents never feel spied on.
No. The agent always shows a visible “monitoring active” indicator while capturing, employees see their own data, and consent is recorded before any capture begins. There is no hidden or stealth mode.
No. WorkPulse measures input presence as counts only — never keystroke content, message bodies, or full page content. Window titles and URLs are maskable and default to domain-only, and screenshots are off by default.
Nothing is captured. Monitoring is strictly bounded to clocked-in working time — enforced both on the device and on the server.
Call state beats idle. During an active call or after-call work, the agent counts as active regardless of keyboard input — via dialer integration, a generic webhook, a configurable on-screen rule, or a manual “I’m on a call” toggle.
A Windows 10 (1809+) and Windows 11 desktop agent, on x64 and ARM64. macOS and other platforms are on the roadmap.
Three tiers that grow from a straight time clock to full call-center fit and enterprise compliance. Tell us your floor size and we'll tailor a quote — no per-seat list price games.
Time clock + activity basics
Everything in Starter, plus call-center fit
Everything in Growth, plus scale & compliance
Worked time is billed by active agents, never by seats you're not using. SOC 2 Type II is targeted before general availability.
Tell us about your floor — headcount, dialer, jurisdictions — and we'll show you a worked-time setup your agents can trust. Already a customer?
Client loginOne click, or auto on unlock. Punches are signed to the device and stamped on server time, so worked-time math never trusts a local clock.