Your first team ritual.

Set up scheduled check-ins

In a public channel, run /sync setup. Choose active human participants who belong to the channel, weekdays, an IANA time zone (for example, Asia/Tokyo), check-in and digest times, and a template. You can also write one to five custom questions.

New setups start Paused. Select Enabled when you are ready, review the preview, then Confirm. Only the workflow owner or a workspace admin can change an existing setup. The scheduler checks for due work every 15 minutes. Delivery may be later during an outage or backlog. Leave at least 15 minutes between the check-in opening and digest so a scheduler run can occur.

Check in, then follow through

During the configured window, use /sync checkin or the Share update button. Answer the questions, optionally add a blocker and a helper, and submit. Each participant submits once per session. At digest time, the channel receives a summary; the full updates remain available in Kick Home.

Open Kick under Apps in Slack and select Home. Choose a channel, then Overview, Updates, Blockers, or Team trends. Use /sync home to refresh it. Home requires the Slack Home tab and app_home_opened subscription; if the tab is unavailable, the existing slash commands still work.

Rotate fairly and celebrate contributions

/pick rotate uses the participant list in an enabled channel ritual to choose the least recently selected person. Exclusions apply to that pick only. The result is queued for the next scheduler run; /pick remains an immediate random pick. Enable the optional Friday appreciation roundup in channel settings to recap new kudos and coins.

Keep reminders on your terms

/sync preferences saves your time zone, quiet hours, leave-through date, and reminder opt-out. Private reminders and helper follow-ups require permission granted to your installation and service activation. Saving preferences does not grant permission or turn on delivery.

To pause, return to /sync setup, select Paused, preview, and confirm. New workflow history uses your selected 7-, 30-, or 90-day retention; core command history and messages stored in Slack have separate retention rules.

Your team workspace in Slack

Open Kick → Home, select a workflow, then choose Open team workspace. Shared records are limited to current members of that public channel. Personal to-dos are separate and visible only to their owner in Kick. These tools do not require a separate login.

Multiple workflows and calendar exceptions

Use Add workflow in Home for an independent schedule in the same channel (up to ten). Give it a distinct name. The original /sync setup, /sync checkin, and /pick rotate commands target the channel’s default workflow; Home buttons target the selected workflow. Owners and workspace admins can use Calendar to skip a date or override its opening and digest times, before that check-in opens. Dates must fall within the workflow retention window.

Personal and channel to-dos

For private tasks, choose My personal to-dos directly in Home—even before setting up a channel workflow. Add text and a due date, edit it, mark it Done or Open, or delete it. Only you can view your personal list in Kick. It never appears in channel lists, search, or reports. Personal tasks expire 30 days after creation; editing does not extend that period.

For shared work, choose Channel to-dos → New action, or Track action while reading an update or blocker. Review the text, choose an assignee and due date, and optionally link a sprint. All current channel members can see that workflow’s list. The assignee, creator, or workflow owner can mark it Done or reopen it. Your open assigned channel actions appear in Home.

Polls

Choose Polls → Create poll. Enter a question and 2–10 different choices, one per line. Create & announce saves the poll and queues an invitation for the channel. Members open it from Home and select Save vote. Each member gets one vote and can change it until closed. Refresh shows current totals. The creator or workflow owner can Close poll and confirm to stop voting permanently and queue final results. Votes are stored with Slack IDs—not anonymously; the interface shows counts rather than a voter list.

Comprehensive reports

Reports also include decisions, objectives, key-result counts, onboarding completion and outgoing handoffs for the selected period. Capacity limits, key-result values, approvals, leave requests and one-on-one records are excluded. Imported issue tasks count as channel to-dos; provider credentials and raw provider responses never appear.

Choose Comprehensive report and a UTC date range of at most 90 days. Build report previews check-ins, blockers, channel to-dos, sprints, recognition, retrospectives, planning sessions and polls for the selected workflow. Share report explicitly queues the current totals for that channel; closing the preview sends nothing.

Reports count retained records created within the dates and show their current status, not a historical snapshot. Expected responses sum participants in runs created in range; updates have their own creation dates. Personal to-dos, legacy command history, coin balances and hidden estimates are excluded. A zero count means no matching retained records, not necessarily no past activity.

Team planning: workload, objectives and decisions

From the team workspace, choose Team planning. These tools use the selected workflow’s records and channel membership. Saving a planning record does not send a channel notification.

View workload shows open channel to-dos due by the selected week’s Sunday, including unfinished earlier work. Weeks run Monday–Sunday; overdue counts use today in the workflow’s time zone. Choose Set my capacity to declare your own task limit for that week. Zero means unavailable; an unset limit means unknown. Only you can change your capacity. The limit is a planning aid, not an assignment restriction, hours estimate or productivity score. Personal tasks, other workflows and external trackers are excluded.

Objectives & results lets you create an outcome with an owner and start/target dates. Add key results with a baseline, current value, target and unit. For example, reducing lead time from ten days to two days is halfway complete at six days. Progress is displayed between 0% and 100% without changing the stored values. The creator, result owner or workflow owner can update a result; only the objective’s responsible owners or creator can add results. Closing an objective prevents result edits until an owner reopens it.

Decision log records a title, proposal or decision, rationale, responsible teammate and review date. Use Proposed, Accepted or Superseded to keep the status clear. Creators, assigned owners and the workflow owner can edit; other channel members can read. Review dates are informational—no automatic reminders are sent.

Planning records follow 7-, 30-, or 90-day workflow retention from creation. Editing does not extend it; key results expire no later than their objective. Target dates, review dates and the end of a capacity week must fall before expiry. For a longer planning cycle, select 90-day retention before creating records. Concurrent edits are checked: if someone else saves first, reopen the form to see their changes.

People & coordination

Choose People & coordination in Home or Team planning. Approvals have one designated approver and a UTC decision deadline; only requester and approver can read details. The approver confirms Approve or Decline with an optional note. Self-approval and approval after the deadline are refused. Cancel and recreate to change the details.

Team handoffs asks you to choose another public channel and its Kick workflow, then write a summary safe for both teams. You and the recipient must belong to both channels. The recipient accepts from the receiving workflow; only then can that channel’s other members read the summary. No source record is copied and saving sends no channel message.

Onboarding gives a newcomer a buddy and a shared checklist with owners and dates. Private one-on-ones provides an agenda and follow-up checklist visible only to its two participants while they remain channel members—not to other admins. Both participants can read every agenda item. Finish open items before completing either kind of checklist. Titles and one-on-one notes are encrypted at rest, not end-to-end encrypted.

My leave requests records future dates, a decision deadline, an approver and a proposed cover teammate. Agree coverage with that person first. Team coverage shows only approved names, dates and proposed cover; it hides the reason and decision notes. Approval does not alter scheduled reminders: set your leave-through date separately in /sync preferences.

Escalation settings is for workflow owners and Slack admins. Enable it explicitly and choose a 1–30-day threshold. An enabled workflow can send one weekday channel summary after digest time, checked every 15 minutes. It reports overdue channel tasks and aging unresolved blockers, not private records. Disable it to stop queued summaries. These settings expire with workflow retention.

Connect your organization’s issue tracker

A Slack workspace admin who belongs to the channel opens Team planning → Issue sync. Connect GitHub, Jira or Linear using the provider’s consent screen. For GitHub, install Kick Team Sync and select repositories before authorizing. Return to Slack, refresh Issue sync, choose the organization or Jira site, and map a repository, Jira project or Linear team. Check that the channel is allowed to see that project.

Choose Preview an issue and enter its key (for example TEAM-42) or GitHub number (42). Confirm the title, Slack assignee and due date before importing. This creates a channel to-do; it copies the title and status, not comments, attachments or private records. The selected provider may need administrator approval or enablement before consent is available.

Open Linked issues → Compare to read current statuses. Use provider status updates Kick; Use Kick status lets you choose a matching provider state or Jira transition. Confirm the direction before applying. If either side changes after the preview, refresh and choose again. Both-side conflicts are labeled; nothing synchronizes automatically. Provider APIs do not guarantee atomic updates against changes made at the same instant, so refresh after a concurrent edit or interrupted request.

Only the Slack admin who connected a provider can operate that account through Kick. Other workspace admins may disconnect it, but cannot borrow its credentials to read or change provider issues. Disconnect workspace deletes Kick’s stored provider credentials and cascading mappings/links, but keeps imported channel tasks and remote issues. Remove mapping affects only that workflow. Revoke provider-side consent in the provider settings if desired. Connections expire after 90 days; mappings and links follow workflow retention. Each workspace uses its own consent—never the app operator’s account.

Editable updates

Read your submitted check-in and choose Edit / correct. Before the digest closes, your saved answers are replaced. After closing, Kick preserves the original and queues a labeled correction. These edits apply to scheduled workflow check-ins, not legacy /sync command records.

Sprint goals and recaps

Owners and workspace admins can create a sprint with a goal and start/end dates. Link actions when creating or editing them. Its detail view includes workflow updates from those dates. Finish & share recap closes the sprint and queues a summary of retained records for the channel. Counts are not productivity ratings.

Retrospectives

Create a retrospective, then add Keep, Improve, or Try topics. The facilitator can group related topics by a shared label, open voting, and close the retrospective. Each member can vote once per topic. Topics can become assigned actions. Names are visible: this is not anonymous feedback.

Planning poker

Create a session and select channel members as voters. Choose an estimate, ? for unsure, or Abstain. Values stay hidden until the facilitator reveals them. After discussion, start another round or record a final decision. Other members should use Refresh to see the latest phase.

Search and operations

Search history searches only the selected workflow’s retained Kick updates, actions, blockers, and recognition—not your Slack message history. Filter by words, person, UTC dates, and status. Owners and admins can inspect installation connectivity, configuration, retained delivery failures, and the audit in Operations. Retry is limited to failed, unleased, unexpired jobs; Slack delivery is not guaranteed exactly once.

Message shortcuts

Open a public-channel message’s More actions menu and choose Track action, Report blocker, or Give kudos. Select a workflow and review the copied text before confirming. Cancel saves nothing. Kudos queues a channel message; actions and blockers are saved in Kick. Attachments and surrounding messages are not copied.

Already using Kick? This release adds no new permissions, so you do not need to reinstall just to use polls, to-dos, reports, or message shortcuts. Reopen Kick’s Home tab or run /sync home to refresh it. If Slack does not show a shortcut, look for it under More message shortcuts and confirm Kick is installed in this workspace. Contact support if it is still missing.

Scheduled sends and explicitly queued recaps, corrections, and thanks are normally checked every 15 minutes. Pausing a workflow stops automatic check-in prompts; explicitly requested channel notices can still be delivered. Workflow records expire after 7, 30, or 90 days; linked child records may expire earlier with their parent.

Try your next team ritual

/kudos thanks a teammate with a reason. /coins sends virtual recognition points—not money. /pick randomly selects eligible teammates. These workflows can post results visible to the channel.

Need a hand?

Type /sync -h for command help. If Slack cannot find a command, check that you selected the workspace where Kick was installed, or ask your workspace admin to approve the app. If Kick reports missing channel access, invite it to that channel and try again.

Kick’s core workflows are free and need no separate account. If you have not installed it yet, use the button below and complete Slack’s authorization screen.

Read the Privacy policy before sharing sensitive information. For help, visit Support or email kick.bot.help@gmail.com.