How to Keep a Discord Bot's AI Chat in One Channel

An AI chatbot that answers in every channel can take over a busy server. Here is how to give Kiki's AI chat a home, limit it to the roles you pick, and keep translation running everywhere else.

Kiki answers when a member says "Hey Kiki", calls her by name ("Kiki, can you...", "hi Kiki"), @mentions her or replies to one of her messages. On a small server that is exactly what you want. On a busy one, a long AI conversation in #general can bury the chat it was meant to help. The fix is to decide where she chats, and it takes one command.

The short version: run /ai_chat_access add_channel with the channel you want, and Kiki The Translator's AI chat answers only there. Translation, flag reactions and "Ask Kiki about this" keep working in every channel.

Why not just change the bot's channel permissions? #

The usual way to keep a Discord bot in one channel is a permission override: take away its Send Messages permission in every other channel. For a bot that only chats, that works. For a bot that also translates, it backfires, because the same permission is what lets Kiki post translations. Remove it and the channel quietly stops being translated, which is the opposite of what a multilingual server wants.

/ai_chat_access limits the AI chat and nothing else. Every translation setup keeps working, flag reactions keep working, and members can still right-click a message and choose "Ask Kiki about this".

Step 1: pick the channels #

Run this anywhere on the server and pick the channel where Kiki should chat:

/ai_chat_access add_channel channel:#ask-kiki

• A category counts too. Add a category and every channel in it is included, even channels you create in it later.
• Threads follow their channel. A thread under an allowed channel is allowed.
• Up to 25 entries. Run the command once for each channel or category.

As soon as the list has one entry, Kiki's AI chat answers only in the listed channels.

Step 2 (optional): pick the roles #

/ai_chat_access add_role role:@Members

With a role list, only members who have one of the listed roles can chat with Kiki. Members with the Manage Server permission can always chat, whatever their roles, so an admin never locks themselves out. When you set both lists, a member needs an allowed role and has to be in an allowed channel. The role list holds up to 25 roles.

Step 3: check it #

/ai_chat_access list shows the channels and roles on the list. Only you see the answer, and anyone on the server can run it.

What members see outside the allowed channels #

If someone says "Hey Kiki" in a channel that isn't on the list, Kiki replies with a short note naming the channels where she chats. The note deletes itself after a minute, and each member sees it at most once every 15 minutes, so a busy channel doesn't fill up with reminders. A member without an allowed role gets no reply.

Change it or undo it #

• /ai_chat_access remove_channel and /ai_chat_access remove_role take one entry off the list.
• /ai_chat_access reset clears both lists, and Kiki chats everywhere again, for everyone.

Changing the lists needs the Manage Server permission.

Three setups that work #

1. One bot channel. Create #ask-kiki and run /ai_chat_access add_channel channel:#ask-kiki. General chat stays human, and everyone knows where to find her.
2. A help desk category. Put your support channels in a Help category and add the category. New help channels you create there are covered automatically.
3. A staff assistant. Add your #staff channel and your @Staff role. Staff get an AI assistant for running the server, and nobody else can start a chat with her.

How members reach Kiki #

Inside the allowed channels nothing changes for members. They can start a message with "Hey Kiki", address her by name ("Kiki, what can you do?", "hi Kiki", "hola Kiki"), @mention her or reply to one of her messages. If someone on your server is also called Kiki, greetings like "hi kiki" are left to them. An administrator can switch the trigger with /ai_chat_trigger so that any message with the word "Kiki" in it reaches her. Only administrators can change the trigger.

What it costs #

Kiki's AI chat on a server is part of the Feline Finest plan: 9 tokens a month ($9), which members can pool, so nine members giving one token each unlock it for everyone. /ai_chat_access costs nothing extra. Server admins can try every Feline Finest feature free for 7 days with /free_trial.

Frequently asked questions #

Can I make Kiki's AI chat answer in only one channel?

Yes. Run /ai_chat_access add_channel with that channel and Kiki's AI chat answers only there. You can add up to 25 channels or categories, and a category covers every channel in it. /ai_chat_access reset lets her chat everywhere again.

Does limiting AI chat stop translation in other channels?

No. /ai_chat_access limits only the AI chat. Translation, flag-reaction translations and "Ask Kiki about this" keep working in every channel. That is the difference from taking away the bot's channel permissions, which would stop translation too.

Can I let only some roles chat with Kiki?

Yes. Run /ai_chat_access add_role with each role. Only members with one of those roles can chat with her, and members with the Manage Server permission always can. Remove a role with /ai_chat_access remove_role.

What happens when someone says Hey Kiki outside the allowed channels?

Kiki replies with a short note naming the channels where she chats. The note deletes itself after a minute, and each member sees it at most once every 15 minutes. A member without an allowed role gets no reply.

Who can change where Kiki chats?

Members with the Manage Server permission can add and remove channels and roles and reset the lists. Anyone can see the lists with /ai_chat_access list. The chat trigger, /ai_chat_trigger, can only be changed by administrators.

Related reading: what's new in Kiki covers this and the rest of the October 2026 update, the step-by-step setup guide covers installing and configuring translation from scratch, and the bilingual server playbook covers the channel structure that keeps multilingual communities together.