Solución de problemas Member Admin

Dailybot isn't responding to my commands

Dailybot isn’t responding to my commands

Dailybot is installed but ignores mentions, slash commands, or DMs you expect to work. Each chat platform enforces its own permission model, so the fix depends on where you talk to the bot. Use the section for your platform first, then the shared checks at the end.

Quick check

Right workspace or server — Confirm you are messaging the Dailybot that belongs to the same org you use in the web app.
Bot presence — Verify the integration shows connected in Dailybot settings and the bot appears online in chat.
Correct command syntax — Slash commands must use the current name Discord or Slack shows; legacy @Dailybot flows differ by platform.
Thread or channel scope — Some commands only work in channels where the bot was invited or where app policies allow.
Plan and feature — A few command families require a paid tier; the bot may not reply if the feature is disabled.

Common causes and fixes

Slack: app permissions

Slack blocks actions when scopes are missing after an update. An admin should open Slack App settings for Dailybot (or your workspace’s approved app directory entry) and compare required bot token scopes to what is granted. Reinstall or approve the updated permission list if Slack prompts. In-channel, ensure /invite @Dailybot ran where needed and that channel restrictions do not hide slash commands. If Enterprise Grid policies apply, check whether the app is allowed on that workspace.

Discord: role hierarchy

Discord slash commands and follow-up messages fail when the bot cannot complete the interaction because of role order or missing Use Application Commands on the channel. See Slash commands aren’t working in Discord for role ordering, registration, and guild permission steps.

Google Chat: admin not enabled

Chat apps must be allowed by your Google Workspace admin. If commands never resolve, ask an admin to verify Dailybot is on the allowlist for Chat apps and that install was completed for the correct space. Users may need to @mention the bot the first time in a space to grant access.

Microsoft Teams: approval needed

Teams often requires admin consent for third-party apps. If the bot never joined a team or personal messages bounce, an IT admin should approve Dailybot org-wide or for the teams that need it. After approval, add the bot to the team channel again. Policy blocks can look like “silent” failures.

Shared: disconnected integration

If OAuth tokens expired or someone removed the app, commands stop. Org admins should open Dailybot Integrations, confirm the platform shows healthy, and use How to disconnect and reconnect your chat platform if refresh is needed.

If none of this worked

Before contacting support, gather:

Chat platform (Slack, Discord, Google Chat, Microsoft Teams)
Workspace, server, or tenant name (non-secret identifier)
Example command that fails and the channel type (public, private, DM)
Whether you are admin on that platform
Screenshots of any error or of the bot missing from the member list
Steps you already tried from this article

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