# Kick Bot > Kick is a Slack productivity bot for async standups, peer recognition, team rewards, and fair random selection. Canonical website: https://kick.bozmoz.com Install: https://kick.bozmoz.com/api/slack/install Support: https://kick.bozmoz.com/support Privacy: https://kick.bozmoz.com/privacy Terms: https://kick.bozmoz.com/terms ## Core workflows - /sync opens an async standup form for mood, yesterday, today, blockers, and optional kudos. - /sync -r 7 returns a report for the previous seven days; the range can be 1 to 30 days. - /kudos lets someone recognize one or more teammates with a reason. - /coins sends a lightweight team reward and records why it was given. - /pick randomly selects one or more eligible channel members and can include a random question. - Add -h to a command for current help in Slack. ## Team-rituals release - /sync setup configures a public-channel workflow with participants, weekdays, IANA time zone, template or custom questions, digest time, and 7/30/90-day workflow retention. It starts paused and requires preview and confirmation. - /sync checkin submits an update during the configured check-in window; blockers can have an assigned helper and be resolved. - /sync home refreshes the membership-aware App Home, which has overview, updates, blockers, and aggregate trends. The Slack Home tab and app_home_opened event must be configured. - /sync preferences saves quiet hours, leave dates, snooze-related preferences, and reminder opt-out. - /pick rotate queues a least-recent selection in an enabled channel ritual; it is not the same as random /pick. - Optional digests and Friday recognition roundups are delivered by an external scheduler with 15-minute checks when activated. Delays can occur during outages or backlogs. - Private reminders and helper follow-ups require permission granted to the workspace installation and service activation. - Getting started and feature availability: https://kick.bozmoz.com/get-started ## Team workspace - In Kick Home, select a named workflow and Open team workspace. Up to ten independent workflows can share a public channel. /sync workflows refreshes Home. - Actions have an assignee, due date and Open/Done status; create them directly or from an update, blocker or retrospective topic. - Channel to-dos is the shared action list for the selected workflow. Example: assign Prepare the release demo to a teammate, due Friday, then mark it Done. - My personal to-dos works directly from Home without channel setup. Tasks are private to their owner in Kick, have due dates and Open/Done status, can be deleted, and expire 30 days after creation. They never enter channel lists, shared search or reports. - Polls accept 2–10 choices and one changeable vote per current channel member. Example: Which day for the demo? Tuesday or Thursday. Creation queues an invitation; the creator/workflow owner closes voting and queues aggregate results. Votes are stored with Slack IDs, not anonymously. - Comprehensive report combines retained check-ins, blockers, channel to-dos, sprints, recognition, retrospectives, planning sessions and polls for the selected workflow over up to 90 UTC days. Preview then explicitly share. Counts use creation dates and current status, not historical snapshots. Personal to-dos, legacy command history, coin balances and hidden estimates are excluded. - Concrete examples for every feature: https://kick.bozmoz.com/#team-rituals - Authors can edit scheduled check-in responses before the digest closes. Later changes preserve the original and queue a labeled correction. Legacy /sync history is not editable through this feature. - Sprint goals have start/end dates, linked actions and workflow updates from the period. Finishing a sprint queues a factual recap of retained records. - Retrospectives support attributed topics, grouping, one vote per member per topic and conversion to actions. They are not anonymous. - Planning poker hides estimates until facilitator reveal, supports abstention and new rounds, and records a final decision. - Search filters the selected workflow's retained Kick updates, actions, blockers and recognition by text, person, UTC dates and status. It does not search Slack message history. - Owners/admins can skip a calendar date or override its times before that session opens; dates must be within the retention window. - Owners/admins can inspect installation connectivity, delivery failures and an audit, and retry failed, unleased deliveries. Slack delivery is not guaranteed exactly once. - Message shortcuts Track action, Report blocker and Give kudos require Slack configuration and publication. They preview selected message text and save only after confirmation. - All new collaboration records follow 7/30/90-day workflow retention. Child records can expire earlier with their parent. Channel notices are checked every 15 minutes and may be delayed. ## Planning and coordination - Team planning includes self-declared weekly task capacity, objectives with measurable key results, and a decision log with owners and review dates. No individual productivity scores. - People & coordination includes cross-team handoffs accepted by a receiving teammate, participant-only approval requests with deadlines, channel-visible onboarding checklists with buddies, and private two-person agendas and follow-ups. - Leave requests have a designated approver. Team coverage shares only approved names, dates and proposed cover; reasons are private. Reminder leave preferences are set separately. - Escalations are opt-in weekday channel summaries of overdue actions and aging blockers; an enabled workflow and scheduler are required. Delivery rechecks current status. - Issue sync is administrator-managed and organization-specific. Connect GitHub, Jira or Linear, select the provider organization/site and repository/project/team, and explicitly preview/import an issue title and status into a channel to-do. Later status changes are manual and confirmed in either direction, with stale-preview checks and conflict notices. There is no background sync, remote deletion, comment/attachment copying or private-record export. Provider consent and availability are required. - One-on-one titles and notes are encrypted at rest and participant-only in Kick, not end-to-end encrypted. New workflow records use 7/30/90-day retention. Provider connections expire after 90 days and may be disconnected sooner. ## Account and pricing Kick does not require a separate user account. Installation and identity are handled by Slack. Core workflows are free. ## Data Kick stores the Slack workspace and authorization information needed to operate, plus submitted workflow records. It does not store team member email addresses. See the privacy policy for retention, export, and deletion details.