Before you start
- A Pro or Enterprise plan.
- You are a workspace owner or admin.
Set up Slack
Add the bot
Go to Integrations → Chat bots, click Add bot and choose Slack. Pick the knowledge bases it answers from. Optionally pick Source groups, or enter a Channel ID to switch it on in that one channel only.
Approve it in Slack
Click Add to Slack, choose your Slack workspace and approve. Without a channel ID, the bot answers in no channel yet.
Inviting the bot to a channel does not switch it on. Anyone in your Slack workspace can invite a bot, so only a Slack admin’s command decides where it answers.
Ask in Slack
| How | What happens |
|---|---|
@Kelu how do I rotate a client key? | Answers in a thread under the question |
| A direct message to Kelu | Answers privately |
/kelu how do I rotate a client key? | Posts the question and the answer for the whole channel |
| A new post in a channel with Forum auto-reply mode on | Answers without a mention |
@Kelu again in the thread to ask a follow-up; it remembers the conversation. Mentioned in someone else’s thread, it first reads up to 20 earlier messages (4,000 characters).
Files attached to a question are used for that answer only and are never indexed: up to 3 files, 5 MB each, 12,000 characters of text in total, in the upload formats. Images (.png, .jpg, .gif, .webp) are read too.
Channels and a second bot
Once a Slack bot is installed, its card shows the command under Switch on in a channel. Run these in Slack. They need a Slack workspace owner or admin.| Command | Effect |
|---|---|
/kelu-enable-channel <integration-id> | Answer in this channel with this bot |
/kelu-enable-workspace <integration-id> | Answer in every channel the bot is in, including any it is invited to later |
/kelu-disable | Stop answering in this channel |
/kelu-disable all | Stop answering in every channel |
/archives/ (it starts with C).
Set up Microsoft Teams
Add the bot
Go to Integrations → Chat bots, click Add bot and choose Microsoft Teams. Pick the knowledge bases, enter the App ID and App password, and click Add bot.
Settings
Click Configure on a bot’s card (older Slack and Discord bots have none; see the note below). Changes apply to the next question. The knowledge bases are chosen when you add the bot.| Setting | Platforms | Default | What it does |
|---|---|---|---|
| Channel ID | Slack | Blank | Answer in this channel only. A bot limited to one channel does not answer DMs |
| Forum auto-reply mode | Slack | Off | Answer every new top-level post in the channel without a mention |
| Answer @ mentions | Slack, Teams | On | Answer when mentioned |
| Answer slash commands | Slack, Teams | On | Answer /kelu |
| Answer direct messages | Slack, Teams | On | Answer 1:1 messages |
| Show feedback controls | Slack, Teams | On | 👍/👎 buttons under each answer |
| User tracking | Slack | Anonymous | Record the Slack user ID, or the person’s email address, with each conversation |
| Voice | Slack, Teams | Knowledge base’s own persona | Answer in a customization |
| Source groups | Slack, Teams | All | Answer only from these source groups |
| Messages | Slack, Teams | Built-in text | Your own wording for Acknowledgment, Acknowledgment in forum mode, Acknowledgment in a DM, Follow-up, No answer found, Error, Withheld for personal data, Footer, Final note and Final note in a DM. Post no acknowledgment turns the acknowledgment off. Teams has Error message only |
Ratings
The 👍/👎 buttons record one vote per answer. The chosen thumb is highlighted and no count is shown. Press your highlighted thumb again to withdraw the vote. On Slack, a 👍 or 👎 reaction on an answer counts as a vote too. Votes appear in Analytics. Bot answers count toward the workspace’s monthly question allowance and appear under Conversations. With zero data retention they still count, but nothing is stored: they do not appear under Conversations, a follow-up does not see the earlier answer, and there are no rating buttons.Discord bots cannot be added from the dashboard at the moment. A Discord bot you already have keeps working, and one on the shared Kelu app can still be configured. Slack and Discord bots created before the shared Kelu app keep working on their own app. Their card has no Configure: it shows only the Webhook URL to paste into that app, and the delete button.
Troubleshooting
- The bot ignores mentions in a channel. A Slack admin has not switched it on there. Run
/kelu-enable-channel <integration-id>in that channel. In a private channel, also run/invite @Kelu. The bot’s Home tab in Slack lists the channels it answers in. - “Kelu is not enabled in this channel yet.” Run
/kelu-enable-channel <integration-id>there, or clear the bot’s Channel ID. - “Only Slack workspace owners and admins can change where Kelu answers.” Ask a Slack admin to run the command.
- A new bot answers nowhere. Expected. Switch it on in a channel with
/kelu-enable-channel <integration-id>. /kelu-disablesays the bot still answers in this channel. It is switched on for every channel. Run/kelu-disable all, then enable the channels you want one by one.- No answer in Teams. Check that the Messaging Endpoint is the bot’s Webhook URL, and that the App ID and password match the Azure registration.