Time tracking,
in Slack.

Punch Bot replaces Jibble. Clock in and out with /log commands, track breaks, and pull monthly reports — all in Slack. Every event posts to #attendance for full team visibility.

Clock in. Clock out. In Slack.

#attendance · live·0 events today
08:58Sajid/log in
09:02Mahroos/log in
09:14Alim/log in
12:31Sajid/log breaklunch
13:18Sajid/log resume
17:42Mahroos/log out8h 40m

Live preview · simplified

Why we built it.

We were paying for Jibble. Nobody used it. People forgot to clock in. Forgot to clock out. Forgot it existed. The standalone-app model only works if the app is somewhere you already are — and our team was already in Slack all day.

So we cancelled Jibble and built Punch Bot in a weekend. Same model — clock in, clock out, breaks, reports. Different surface — Slack commands and a public #attendance feed. Adoption went from <30% to 100% the first week.

The best time-tracking app is the one your team already has open all day.

What's inside.

01Four commands. That's it.

/log in starts a session. /log out ends it. /log break pauses the timer. /log resumepicks it back up. That's the whole vocabulary. No buttons, no menus, no app to install.

Every command posts to #attendancewith a timestamp, so the team gets full visibility without anyone having to ask “is X around today?”.

02Breaks count. Just not toward your hours.

A break is a pause in the running timer. The session stays open, the clock stops counting billable time, and the team sees you're away. Resume when you're back. The break duration appears in the daily total so it's clear what was on-the-clock vs off.

Active break · Sajid·since 12:31
break · counting
00:00:00
Lunch break in progress

03Monthly reports, generated.

On the first of each month, Punch Bot DMs the admin a clean monthly report — per-person hours, per-day breakdowns, breaks deducted, and a row-level audit trail. Drops as CSV for payroll import, or stays in Slack for a quick eyeball.

April · monthly report·4 people · 660 h
Sajid
168h
Mahroos
162h
Alim
174h
Wazir
156h
Avg / person165 h

04Edits without erasing history.

Forgot to clock out? /log adjust opens a small dialog asking for the corrected time and a reason. The original timestamp is preserved in an audit field — nothing gets quietly rewritten — and the corrected entry shows up in the next report.

Under the hood.

Six things that make it more than a slash command.

  • Public attendance feedEvery event posts to a single channel. No one has to ask who's online — it's already there. Manager visibility without a status meeting.
  • Supabase persistenceSessions, breaks, edits all stored with timestamps and audit fields in Supabase. Reports query directly — no separate analytics layer.
  • Auto-flag long sessionsAnything over 14 hours triggers a soft reminder in #attendance and a DM to the user. Catches forgotten clock-outs before they pollute the report.
  • Audit-trail editsAll time corrections preserve the original timestamp + reason. /log adjust never silently rewrites — corrections are first-class entries.
  • Per-team configurableWorking hours, break rules, and overtime thresholds are per-team JSON. Swap the config, no redeploy.
  • CSV export for payrollMonthly reports drop as CSV with per-person totals, breaks deducted, and per-row entries. Direct paste into payroll sheets.
100%
team adoption, week one
4
slash commands, total
0
external apps to install
1st
of every month, report drops

A few questions.

Anything else: hello@practa.ai.

We did. The friction killed it. Standalone time-tracking apps live outside the tools you actually use, so they get forgotten. Punch Bot lives in Slack, where the team already is — clocking in is one slash command in the channel where you'd post 'morning' anyway.

Punch Bot auto-flags any session over 14 hours and posts a soft reminder in #attendance. The session can be edited after the fact via /log adjust, with a reason. The audit trail keeps the original timestamps.

Yes — monthly reports drop as CSV with per-person totals, breaks deducted, and a row-level audit trail. Goes straight into a payroll spreadsheet or import.

Cancel the time-tracking app. Use Slack instead.

Punch Bot is one of the workflows we ship under the standard Practa subscription. Tell us your stack — we'll build the right Slack-native time tracker for it.