How to force clock in/out from User Status

Sometimes the timeclock and reality disagree. An agent is at their desk but shows as logged out, or has gone home but still shows as on the clock. The User Status page has a FORCE control for exactly these moments, and using it correctly keeps your reported hours honest.

What forcing actually does

The timeclock is the daily punch system that records when an agent starts and ends work, kept separate from logging into the agent screen to take calls. When you force a punch from the User Status page, you write a real timeclock record on that person's behalf. Force log in creates a login punch; force log out creates a logout punch. The agent does not have to click anything — the manager does it for them, and the record reflects the corrected state.

Because this is a manager acting on someone else's behalf, the system marks the result. A forced logout leaves a marker on the punch record, so anyone reviewing the timeclock later can tell a forced punch apart from a normal one. That marker is your friend: it means you can use the FORCE control freely without muddying the audit trail.

The steps

1. Open the User Status page for the person. The fastest route is the Real-Time screen — click through to the Agent whose punch looks wrong.
2. Read the current state. The page tells you whether the user is logged into the timeclock and when they logged in.
3. Pick the FORCE option that matches the correction: force log in if they should be on the clock, force log out if they should be off it.
4. Confirm. The punch is written, and a forced logout shows a marker on the record afterward.

flowchart TD
  A[Manager opens User Status] --> B{Is the punch correct}
  B -->|Yes| C[Do nothing]
  B -->|Shows out but is working| D[Force log in]
  B -->|Shows in but has left| E[Force log out]
  D --> F[Login punch written]
  E --> G[Logout punch written with marker]

When a manager actually uses it

You will not touch the FORCE control most days, and that is normal. It earns its keep in a handful of recurring situations.

• A browser crash or dropped Agent session ended a shift without a clean logout, leaving the person stuck as clocked in overnight.
• An agent forgot to clock in at the start of the shift but has been working for an hour, so their hours would otherwise read short.
• Someone left early without punching out, and you want the User group totals to reflect when they really stopped.

In each case the goal is the same: make the timeclock match what actually happened so payroll and adherence numbers stay trustworthy. Forcing the right state takes seconds and saves a confusing reconciliation later.

Force now, fine-tune later

The FORCE control fixes the in-or-out state immediately, but it does not let you set an exact backdated time. If an agent should have clocked out at 5:02 and you only force the logout at 6:00, the punch lands at 6:00. To set the precise login and logout times on a finished record, you edit it on the User Stats page instead, where you can type exact times and add a note explaining the change. The two screens work as a pair: Status flips the state fast, Stats corrects the detail.

For the full picture of how the punch system works, see our guide to the VICIdial timeclock, and for the deeper editing flow read how to edit a record as an admin. The whole operations cluster is mapped in the scheduled callbacks and timeclock overview.

A correct timeclock keeps your hours and your reporting aligned, and forcing a punch is the cheapest way to keep one stray mistake from spreading. If you would rather skip running the platform yourself, VICIfast stands up a branded, hardened VICIdial with the full timeclock toolset in under 40 seconds — see our pricing for the details.