Keito for Slack is here: track time where your team works
A client call finishes. A code review turns into a debugging session. A quick question becomes half an hour of project work.
These moments are easy to discuss in Slack and easy to forget when it is time to complete a timesheet.
Keito for Slack is now generally available on Solo, Pro and Business. You can start and stop timers, log completed work, check your current timer, and view hourly project budgets from Slack. Owners and administrators can also share an hours-only budget summary to an approved internal channel.
It brings everyday time tracking closer to the conversations where work happens, while keeping your entries, projects and permissions connected to Keito.
From a conversation to a time entry
When you are about to begin work, type /keito start.
Keito opens a form where you choose a project and task, add any required notes, and start your timer. The picker uses your existing Keito access, so you see the projects and tasks you are allowed to track against.
That starts the same timer you see in Keito. You can check it from Slack with /keito status and stop it with /keito stop.
If a timer is already running, Keito asks whether you want to keep it or switch to the new task. That helps when a conversation interrupts work you are already tracking: you make the decision about what happens next.
You can also open Keito’s Home tab in Slack to see your connection status, a snapshot of your timer, and today’s tracked time. Refresh the view when you need an updated snapshot.
Already finished the work? Log it from Slack
Some work happens before you remember to start a timer.
Perhaps you have just spent 30 minutes reviewing a proposal, or an unscheduled support call has finished. You can record that work while the details are still fresh.
For example:
/keito log 0:30 Proposal review
This opens a manual-entry form with the duration and note filled in. Choose the appropriate project and task, review the details, and save.
For 90 minutes, you can use either 1:30 or 1.5.
Logging completed work does not stop a timer that is already running. Your entry appears in Keito alongside time recorded through the web app and other integrations, and you can review or edit it in Keito’s Day view.
Here are the main commands:
| Command | What you can do |
|---|---|
/keito connect |
Link your own Slack and Keito accounts |
/keito start |
Choose a project and task, then start a timer |
/keito stop |
Stop your current timer |
/keito log 1:30 Retro notes |
Open a form for 90 minutes of completed work |
/keito status |
Check your current timer |
/keito budget |
View an hourly project budget your permissions allow |
/keito help |
See the available commands |
Keep project hours in the conversation
Time tracking becomes more useful when it helps a team decide what to do next.
Before agreeing to another round of changes, taking on an extra task, or planning the next delivery, run /keito budget.
For a supported hourly-budget project, Keito shows the budget period, hours used, total hours, and remaining hours or overage. Each result includes a snapshot time so you know when the figures were calculated.
Imagine a project with a 40-hour budget and 31 hours already used. Seeing nine hours remaining gives the team a concrete starting point for discussing priorities and scope.
The response is private to the person who requested it. Keito checks your current budget permissions before showing the figures; access to a project alone does not automatically grant access to its budget.
Share a useful update with your team
Sometimes the whole project team needs the same picture.
A linked Keito owner or administrator can share an hourly budget summary to an approved public internal channel in Slack. The flow is deliberate: approve the destination in Keito, select the project, review the exact preview, and confirm the post.
Channel approval can also be restricted to a specific project.
That makes it easier to bring current hours into a planning discussion without asking everyone to open a report. A team can use the summary to discuss remaining work, decide what fits within the available hours, or identify a scope conversation that needs to happen.
Shared summaries contain hours rather than financial details. Rates, costs, monetary budgets, time-entry notes and per-person breakdowns stay out of the budget message.
Keito checks permissions, approval and channel eligibility again before delivery. Private, externally shared, Slack Connect and other unsupported channels are excluded. Once posted, a summary is visible to everyone with access to that channel, including future members.
Less administration between tasks
The main benefit is a shorter path between doing work and recording it.
For an individual, that might mean logging a client call immediately after it ends. For a developer, it might mean starting a code-review timer from the same place the review request arrived. For a project lead, it might mean checking remaining hours before committing the team to more work.
These small actions can make time tracking easier to keep up with throughout the day. They also reduce the amount you have to reconstruct from memory later.
Your records remain together in Keito. Slack is another way to capture and check time, using the same project structure and access rules your workspace already has.
Your account and permissions stay yours
Connecting a Slack workspace and linking an individual account are separate steps.
A Keito owner or administrator installs the app. Each member then links their own account, connecting their Slack identity to their own Keito account, including a final confirmation back in Slack.
Your existing Keito permissions continue to apply. Team members track their own time, budget visibility follows current permissions, and workspace connections and channel approvals remain under owner or administrator control.
Keito requests three Slack permissions: commands, chat:write and channels:read. These support slash commands, responses and approved posts, and checks on eligible public channels. Keito does not request message-history access or read your channel conversations.
Get started
Keito for Slack is available to workspaces with an active Solo, Pro or Business subscription, or an eligible trial.
- As a Keito owner or administrator, open Settings → Integrations → Slack.
- Select Add to Slack, check the destination workspace, and review the permissions.
- Complete any app approval required by your Slack workspace.
- Run
/keito connectin Slack and open the link to sign in to your own Keito account. - Return to Slack, run
/keito connectagain, and confirm the masked account shown. - Try
/keito start, or log a piece of completed work.
Each teammate completes their own account link. You can install directly through Keito without requesting beta access.
Read the Slack setup guide for the complete walkthrough, screenshots, permissions and channel-sharing instructions—or open Keito and connect your workspace today.