How daily team check-ins work
The check-in is the only thing Eodly asks of your team, and it is deliberately small. One short message, in the tool they already have open, once a day.
What a teammate sees
At 9:00 in the morning, in each person's own timezone (or the workspace's, if theirs is not set), the Eodly bot sends them a direct message asking for a quick update: what they shipped or moved forward, anything blocking them, and what they are picking up next. They reply any time that day, in their own words. Each person is messaged on one tool only, Slack first, then Telegram, then Discord, depending on which they are linked to.
- Slack and Telegram: they reply to the DM.
- Discord: they type
/checkinin any channel and fill in the box, and Eodly replies privately. Their first/checkinlinks their Discord account automatically. From then on the morning DM reaches them there too, and they can answer it by typing/checkinright in that DM. A plain reply to the DM is not recorded, because Discord only passes Eodly the/checkincommand. You can also set their Discord id on the Team page. - Microsoft Teams: coming soon, through the Teams Store.
That is the whole interaction. Importing your roster from Slack sets each person's timezone for you, so a teammate in Lagos and one in Warsaw are each asked at the start of their own day, not yours.
They never create an account, never see a dashboard, and never attend a meeting. Anyone who has not replied by 45 minutes before your report time gets one friendly reminder on the same tool, so chasing people is not your job.
What makes a good check-in
Free text is fine. Eodly parses it into claims, so plain sentences work better than formatting:
Finished the billing webhook and opened the PR. Started on the retry logic, blocked on the Stripe test keys.
That gives Eodly three things: something shipped, something in progress, and a blocker. It will then look for the pull request to sit next to the first claim.
Nobody is required to type
If someone does not check in, they are not invisible. Eodly still reads GitHub and Linear, so a silent teammate who merged three pull requests shows up as having shipped. The check-in adds intent, which is what lets Eodly spot the gap between what someone said and what actually moved.
What you get
At your report time, all of it is distilled into one page: who shipped with proof, who is silent, and who is slipping. See Reading your evening report.
This is not monitoring
Eodly reads the check-ins your team chooses to write and the work systems you connect. It does not do keystroke logging or screen capture, and it never will. It is a chief of staff for you, not surveillance of them. Being straight with your team about that is usually the difference between a routine that sticks and one that quietly dies.