Kick bot not responding: how to fix it

Kick only lets a bot post in a channel where it is a moderator. Type the mod command for your bot in your own Kick chat. For StreamNeeds that is /mod streamneeds. If the bot used to work and stopped, check it was not unmodded by accident, for example when you cleaned up your mod list.

Bots read your chat through a connection you approved on Kick. If that approval expired or was removed, the bot cannot see commands at all. Open the bot's integrations page, disconnect Kick and connect it again.

Make sure the command is switched on, spelled exactly the way viewers type it, and starts with the prefix the bot expects, usually an exclamation mark. If your bot has cooldowns, look at those too: a command with a long cooldown answers once and then stays quiet.

Many commands can be limited to mods, subs or the streamer. If a viewer says the bot ignores them while it answers you, the command's permission is the likely cause.

Timed messages that never post are usually waiting on a rule: some only post while you are live, and some wait for a number of chat messages between posts. A quiet chat on an offline channel keeps them silent by design.

If you run more than one bot, two of them can own the same command name. Remove it from one, or rename it, so viewers get one clear answer.

If none of the above helps, the bot itself may be down or delayed. Check its status page or Discord before changing your settings.

The Kick setup page shows whether StreamNeeds is a moderator in your channel and lets you check again after you type /mod streamneeds. Check the bot is switched on for your channel, and that a command is enabled and not set to mods only. StreamNeeds timed messages on Kick post only while you are live, at least two minutes apart. The same bot runs in your Discord, with one points balance shared between the two.