Skip to content
Explicação Admin team-manager Member

Check-ins overview and key concepts

Check-ins overview and key concepts

A check-in is a scheduled set of questions Dailybot sends to selected people. Each participant answers in a direct message (DM) with Dailybot on your chat platform (or via the web). When responses are in, Dailybot compiles them into a report and delivers it where you configured — usually a team channel, and always visible in the web dashboard for people with access.

Check-ins replace live standup meetings for many teams. The same flow supports standups, retros, mood polls, and custom workflows: ask on a schedule, collect privately, share the summary.

Key concepts

Participants are the users who receive the check-in and are expected to respond. You can target individuals, teams, or groups your organization uses. Only participants get the DM; everyone who can see the report destination sees the compiled output (subject to channel permissions on Slack, Discord, Google Chat, or Microsoft Teams).

Questions define what you collect: open text, multiple choice, scales, blocker flags, and conditional follow-ups. Questions belong to the check-in and can be edited by people with the right permissions.

Schedule controls which days the check-in runs, at what local time, and which timezone anchors the org-wide default. Participants can override timezone and reminder preferences in their own settings so “9:00 a.m.” means their morning, not someone else’s.

Report destination is where the compiled report goes after the collection window — for example #standup or a Teams channel. You can still review history and drill into answers from the Check-ins area on the web.

Check-in owner (and org admins) typically configure questions, schedule, participants, and destination. Team Managers and Org Admins can create check-ins; ownership can be assigned or implied by who manages the check-in. Members respond and may edit their own answers within the rules you set.