Answer community questions
Give members a direct path to an employee's approved knowledge. Instead of waiting for whoever is online, someone asks in the channel and gets an answer grounded in what you actually trained that employee on.
Discord
Discord is a planned channel for bringing an AI employee into the servers and direct messages your community already uses. It will connect the same way Slack does today: authorize a bot through OAuth, then map it to one employee. It is not available to connect yet, so no Discord traffic reaches an employee until it ships. Slack, Telegram, each employee's own email address, and web chat cover the same job in the meantime.
Discord is the planned community channel for teams that already coordinate in servers. An employee will answer in approved channels and DMs while using the same tools, training, memory, and guardrails as the rest of the platform.
The goal is a useful participant, not a bot that interrupts every conversation. Server scope and response rules will keep the employee quiet until a person asks for help.
Discord is not connected yet. The bot authorization and server mapping will be managed from the channel drawer when the integration is released.
It is planned to connect the way Slack already does. You authorize a bot into the server you choose, then map that bot to one employee, and that is the whole setup. There is no menu tree to design, no keyword routing to maintain, and no second persona to write, because the employee answering in Discord is the one you already hired and trained.
A channel changes how a message arrives, never who answers it. Whatever a member asks in an approved channel becomes an ordinary request for that employee, which runs it with the same skills, duties, tools, training, and memory it uses in web chat. Anything that needs your approval still waits for you, so putting an employee into a busy server never quietly widens what it is allowed to do on its own.
The reply is planned to go back into the thread the question was asked in, with the whole exchange written into the employee's history inside the workspace. A support answer given in a public channel at midnight would be readable and searchable on a laptop the next morning, sitting next to everything else that employee did. A conversation started in Discord could then be picked up in web chat without anyone repeating the background.
Nothing has to wait in the meantime, and nothing you build now is wasted. Slack is live and covers team workspaces and shared channels, Telegram is live for messaging from a phone and group chats, every employee has its own email address, and web chat is always open. Employees, skills, duties, training, tasks, and memory belong to the employee rather than to a channel, so the employee you train today is the one that answers in Discord the day it ships.
A Useful Server Participant
Ask an employee for answers or actions in the Discord spaces where your community already works.
Members ask in the channel they are already sitting in and get an answer there, rather than being told to open a ticket, email an address, or wait for whoever is awake. For a small team running a community server, that is the difference between questions getting answered and questions quietly piling up.
Scoped by Design
The planned connection will use approved servers, channels, and direct messages rather than listening everywhere.
You decide which servers and which channels the employee is present in, so it never listens across an entire server by default. That keeps it out of the social channels, the off topic threads, and anywhere the conversation was never meant for it in the first place.
Same Workforce Controls
The employee's existing permissions and approval rules still apply.
Guardrails, approval steps, and tool permissions follow the employee rather than the surface it happens to be answering on. An employee that has to check with you before sending an email still checks with you when the request arrived from a Discord thread at two in the morning.
How It Works
A planned Discord bot will route approved messages to one employee and reply in context.
The connection will authorize a bot, map it to an employee, and pass only permitted conversations through the normal dispatcher and channel gate.
Only the conversations you approved get through. A message from an approved channel or a direct message becomes ordinary work for the mapped employee, which runs it with the same skills, tools, duties, training, and memory it uses everywhere else, and pauses for your approval on anything that needs it.
The reply is posted back into the thread the question came from, and the exchange is written into the employee's history inside the workspace. Nobody has to copy an answer out of Discord to keep a record of it, and you can carry the same conversation on in web chat later without repeating yourself.
Use Cases
Support an internal server
Handle recurring requests in a dedicated operations channel. The questions that come up ten times a week stop landing on the one person who happens to know the answer.
Keep responses in context
Reply where the question was asked instead of copying it elsewhere. The thread stays readable for everyone who scrolls it later, including the next member with exactly the same question.
Cover the hours nobody is watching
A question posted in the middle of the night gets a real answer rather than sitting unread until morning, and anything the employee cannot settle on its own is waiting for you with the context already attached.
Comparison
| Before | After |
|---|---|
| A question posted in your server waits for whoever happens to be online. | Once connected, the employee answers in the channel it was asked in. |
| Running community support means somebody watching a server all day. | The employee handles the repeats and leaves you the ones that need judgment. |
| Answers given in chat vanish into scrollback and never reach your records. | Every exchange is written into the employee's history and stays searchable. |
| Every new community app means building and then babysitting another bot. | A channel is just a doorway onto the employee you already trained. |
FAQ
Is Discord available now?
No. Discord is planned and not connected yet, so no message in a Discord server or direct message reaches a Sistava employee today. Slack, Telegram, each employee's own email address, and web chat are all live and cover the same job in the meantime.
Can my AI employee answer questions in my Discord server?
Not yet. Discord is a planned Sistava channel and nothing routes through it today, so a message in your server does not reach an employee. When it ships, you will authorize a bot into the server, map it to one employee, and it will answer in the channels and direct messages you approved. Slack already works exactly that way today.
Is the Discord channel something I can connect today?
No. Discord appears in your channel list under Settings, then Technical, then Channels, marked as coming soon, with no connect button and no traffic behind it. It is deliberately kept out of the set of channels allowed to carry messages, so nothing disappears quietly while the integration is unfinished.
Will the employee reply to every message in the server?
No, and that is the design. The planned connection is scoped to the servers, channels, and direct messages you approve, and the employee answers when someone asks it something rather than commenting on everything it can see. Social channels and off topic threads stay untouched unless you add them yourself.
Can I use an AI employee in Discord direct messages as well as channels?
That is the plan. Direct messages and approved server channels are both in scope, so a member can ask privately or in the open and reach the same employee either way. The conversation lands in that employee's history inside the workspace no matter where it started.
What is the closest thing to Discord that already works?
Slack is the closest match and it is live now, covering team workspaces, shared channels, and direct messages. Telegram is live for group chats and phone messaging, every employee has its own email address, and web chat is always open. A conversation started in any of them continues in any other, because the history belongs to the employee rather than to the app.
Will it answer every server message?
The planned experience is scoped to approved channels and direct messages.
Will it share memory with web chat?
Yes, shared employee memory is the intended behavior.
Where Discord fits
Discord is part of Ways you talk to them.
Chat in the app with live reasoning, speak to your AI voice agent over a call, message on Slack or WhatsApp, send an email, or embed a widget on your website. Every channel connects to the same AI agent with the same memory and capabilities. Switch channels mid-conversation and your employee picks up right where you left off.
- Ways you talk to them: Every channel. One conversation.
Read the guide
More in Channels
- Web Chat: Chat with any AI employee directly in the workspace, with a streaming reply, a live execution timeline showing what it is reading, thinking, and doing, and inline approve/reject buttons when it needs a sensitive action confirmed. It is the default channel: nothing to configure, works on desktop or mobile, and every conversation persists so you can pick it back up later.
- Voice Calls: Voice Calls is a planned channel for speaking to an AI employee out loud and hearing it reply in real time, instead of typing. It is not available yet: there is no voice button in the workspace today, and the feature is paused while the underlying voice flow is redesigned. When it ships, a voice call will run through the same skills, tools, and memory as a typed conversation.
- Connect an Email Provider: Point your own SendGrid, Mailgun, or Postmark inbound-parse webhook at a tenant-scoped endpoint and every email that lands there gets turned into work for an employee. Forward support requests, sales inquiries, or internal approval emails and the employee reads the sender, subject, and body, then acts on it in the background. You get a 202 response immediately; there's no waiting on the request.
- Personal Mailbox: Every employee gets its own email address on the shared Sistava domain the moment you hire it, no setup. Email it directly, CC it on a thread with other people, or forward something over, and it reads and replies within seconds. Free to send from, with a monthly cap by plan. Control the shared employee signature in Company Profile, or connect your own Gmail or Outlook when you want it sending as you, with no cap.
- Send from Gmail or Outlook: The built-in employee address is free and always on, but it sends as the employee, not as you. Connect your own Gmail or Outlook instead and an employee sends and replies from your real address, in your name, with no monthly sending cap on any plan.
- Talk to Your Employee on Video: In-App Video is a planned channel for live, face to face video calls with an AI employee, camera and microphone, directly inside the workspace. It has no working implementation today: it appears in Settings > Technical > Channels as a Coming soon placeholder only. Once it ships, it is meant to run on the same execution pipeline as every other channel, so the employee keeps its skills, tools, training, and conversation memory on a video call. If you need an employee in a live call today, it can already join a Google Meet, Zoom, or Microsoft Teams meeting as a participant, which is a different capability and available now.
- Chat Widget: The Chat Widget will let you embed an AI employee directly on your public website so visitors can ask questions and get answers without leaving the page. It is on the roadmap and is not available to configure yet: today it appears in Settings > Technical > Channels as a Coming soon placeholder with no setup, embed snippet, or Manage action.
- SMS: SMS is a planned channel for reaching an AI employee by ordinary text message, with no app to install. It is on the roadmap and not available today: there is no SMS number, no inbound texting, and no way to turn it on yet. Until it ships, use web chat or Telegram for mobile access from any phone.
- WhatsApp: WhatsApp is a planned messaging channel for talking with an AI employee from your phone. It is not connected yet: the card shows as coming soon and cannot be set up today. When it ships, it will carry the same employee memory, skills, and guardrails as web chat, Telegram, Slack, and the mailbox. Telegram and Slack are live now and give you the same access from a phone, so nothing you set up today has to be rebuilt when WhatsApp arrives.
- Calendar Invites: Add your employee's personal address as a guest on any Google, Outlook, or Apple calendar event and they show up for the meeting automatically, no RSVP or extra app on your side. Once the meeting starts, the employee joins the Meet, Zoom, or Teams call, listens, speaks when addressed, and writes a summary afterward. There is nothing to switch on for the invite itself, just turn on the Meeting Attender tool for that employee once.
- Slack Channel: Bring your AI employee into Slack as a real bot user your team can mention, DM, or trigger with a slash command. Every reply lands in the same thread, and memory, tasks, skills, and tools stay shared with web chat, so a conversation started on Slack continues anywhere else. You approve or reject requests right from Slack, and the bot only speaks when mentioned, DM'd, or already in a thread.
- Telegram Channel: Connect an AI employee to its own Telegram bot so you can message it from your phone the same way you message a person. It answers direct messages instantly, and joins group chats where it replies only when mentioned or replied to. Memory, tasks, and tools are shared with the web app, so a conversation started on Telegram picks up right where it left off on the desktop, and back again.