Try the Live Kiosk Demo Before You Sign Up

You want to know one thing before you commit: will your volunteers, your line cooks, or your event crew actually be able to punch in without you standing next to them? You can answer that in about ninety seconds without creating an account, without giving an email, and without touching a single real name from your team. Open the live kiosk demo and act like you're a worker walking up to the tablet at the front desk.

What you see the moment the demo loads

The screen you land on is the kiosk itself, the same view a worker would see on a shared tablet propped by the door. It shows a grid of names, each one a large tappable tile. There is no username box, no password field, no "create account" prompt. That absence is the point. Workers never sign in, so the first screen they hit is the last screen they need.

Look at the sample names in the grid. In a real workspace those are your people, and you can call them whatever fits your setting: volunteers, staff, crew, tutors. The demo uses placeholder names so you can poke at the flow without setup. Nobody's real hours are involved.

Tapping a name and clocking in

Pick any name and tap it. The kiosk opens that worker's tile and shows their current status. If they're off the clock, you get a single clear action to start a shift. Tap it.

Two things happen. First, the demo records a start time. Behind the scenes that time is stored in UTC and shown back to you in your own local time, so a worker in a different timezone still sees the clock read correctly. Second, the tile flips to an on-the-clock state, usually with a running indicator so the next person walking up can tell at a glance the punch registered. That confirmation matters more than it sounds. When a worker isn't sure the tap worked, they tap again, and you end up with duplicate entries to clean later.

Notice what you were not asked to do. No PIN. No app download. No signup screen between the name and the timestamp. That is the entire pitch in one gesture: the barrier to logging a shift is a single tap.

The who's-on-the-clock view an admin actually watches

Once you've clocked a demo worker in, the value on the admin side becomes concrete. In a live workspace, only admins sign in, and they do it by magic link rather than a password. The dashboard shows who is on the clock right now: a plain list of every worker with an open shift and how long they've been at it.

Clock a second name in to see the list grow. This is the view an event lead glances at from a phone to confirm the whole crew checked in, or a restaurant owner checks before running numbers at close. You are not watching screenshots or a map. There is no location tracking and no activity monitoring, and there never will be. The dashboard answers one question, who is working, and stops there. If you want the reasoning behind that boundary, the answers to common questions spell it out.

Clocking out, and the forgotten-punch problem

Go back to the kiosk, tap the same name again, and choose to end the shift. The tile returns to its off-the-clock state and the entry now has both a start and an end. That closed entry is what eventually lands in a report.

Now consider the case the demo is built to reassure you about: the worker who taps in and walks out at the end of the night without tapping again. Every kiosk deals with this eventually. Kangaroo Clock handles it with auto-close on forgotten clock-outs. A stale open entry gets closed at its start time plus a cutoff you set, never at the current time. So a shift someone forgot to end shows a bounded number of hours instead of ballooning to 40 because nobody tapped out on Friday. Your reported hours don't inflate from human forgetfulness.

Turning demo taps into a report you can hand off

The demo focuses on the worker-facing flow, but it's worth knowing where those taps go. Every entry you create feeds a CSV export with a stable column schema that does not change shape between exports. It includes a distinct-worker count, which is exactly the field a grant report or a payroll handoff tends to ask for. You can tag entries by event or role and group workers by program, then filter the report down to just the numbers you need.

To be clear about the boundary: Kangaroo Clock is not a payroll processor. It does not move money or cut checks. It produces the clean hours file you or your accountant feed into whatever pays people. If you want to see how raw punches convert into the format payroll expects, the time card calculator lets you play with real numbers.

What to do after the demo

Run the loop a couple of times: tap a name, clock in, check the live list, clock out. If the flow makes sense to you in the demo, it will make sense to a first-time volunteer standing at your front desk with a line forming behind them. That is the real test.

When you're ready to put your own names on the grid, you can start a free workspace in a few minutes. Pricing is flat and does not change with headcount, so adding your tenth or your hundredth worker costs the same. The demo is where you decide it's worth it. Go tap a name.