Troubleshooting Admin

Dailybot isn't posting reports to my channel

Dailybot isn’t posting reports to my channel

Quick check

Bot membership — Invite @Dailybot (or your platform’s Dailybot app identity) to the channel where summaries should land. Private channels require an explicit invite; the bot cannot post where it is not a member.
Report destination — In the check-in settings, open the delivery or Report / Summary destination field. Confirm it points to the channel you expect, not a retired channel name or a DM fallback.
Channel permissions — On Slack, the bot needs permission to post messages in that channel. On Teams, verify the bot is installed in the team that owns the channel. Restricted or moderated channels sometimes block apps until an admin approves.
Timing — Many check-ins compile and post after the response window closes (for example, end of day). If you are checking at noon, silence may be normal until the configured compile time.

Common causes and fixes

Bot not added to the channel

This is the most common cause for private channels and renamed channels. /invite @Dailybot in Slack or use the platform equivalent. Re-open the check-in destination picker and re-select the channel so the stored ID refreshes if the channel was recreated. Public channels still require the app to be allowed in that space under your org’s rules.

Report destination misconfigured

Admins clone check-ins, change team structure, or edit JSON-style IDs during migrations. The UI might still show a label while the underlying channel ID is stale. Clear the destination, save, then pick the channel again from the picker. For multi-workspace setups, confirm the destination workspace matches where members respond.

Channel permissions restrict bot posting

Slack workspace settings can prevent posting in certain channels or require admin approval for new apps in private areas. Teams channel moderation can hold messages in review. Test by asking Dailybot to post a short test from the product’s “send test” or troubleshooting tools if available, or temporarily use a public channel as the destination to isolate a permission problem.

If none of this worked

Before contacting support, collect:

Platform (Slack, Discord, Google Chat, Teams) and workspace or team name
Channel name and whether it is private
Check-in name and screenshot of report destination settings
Approximate time you expected a report and whether any participants submitted responses
Whether the bot posts elsewhere (for example, DMs work but channel posts do not)

Then contact Dailybot support from the Help or Contact options in the product or on the website.

Want to go deeper? See the Dailybot Academy for how summaries fit async standups.