Troubleshooting & FAQ
This page answers the questions that come up most often when running your Raileon assistant in Discord and Telegram. If your bot isn't replying, start with the checklist below — most issues come down to one of a handful of settings.
Coming soon
Channels aren't switched on yet. These guides are published early so you can get familiar with the setup — the steps won't work until channels go live in your dashboard. We'll remove this note the moment they do.
My bot isn't replying — what do I check?
Work through these in order. Each one is a real reason a bot stays silent, and the first few are the most common.
1. (Discord only) Is "Message Content Intent" turned on?
This is the single most common reason a Discord bot connects fine but never replies. Discord hides the text of messages from bots unless you explicitly grant permission. Without it, your assistant receives your message but sees it as empty, so it has nothing to answer.
To fix it:
Open the Discord Developer Portal
Go to discord.com/developers/applications and sign in, then click the application you created for your bot.
Open the Bot settings
In the left-hand menu, click Bot.
Turn on Message Content Intent
Scroll down to Privileged Gateway Intents and switch on Message Content Intent. Click Save Changes.
This setting applies to your whole bot — it can't be turned on for just one server. Telegram has no equivalent setting, so you can skip this step for Telegram bots.
2. (Discord only) Did you @mention the bot?
In a Discord channel (a shared space inside a server), your assistant only
replies when you @mention it directly — for example, typing @YourBotName
followed by your question. It does not reply to ordinary messages that don't tag
it. If you want a reply without mentioning the bot, send it a direct message
instead — in DMs, the assistant replies to everything you send.
On Telegram, this is different — see "Why does it only reply when I mention it?" below.
3. Is the channel connected and added?
A bot being a member of a channel is not enough — the channel also has to be added in your Raileon dashboard. If you never added it, the assistant quietly ignores messages there.
To check, open Channels in your dashboard and look at the Connected channels list. If the channel isn't there:
Connect the bot
In the Connect a bot section, choose your platform from the Platform dropdown, paste your bot token into the Bot token box, and click Connect.
Find the channel
Under Channels [platform] can serve, look for the channel you want.
Add it
Pick Staff from the dropdown next to the channel, then click Add. It will then appear in your Connected channels list.
If the channel you want isn't showing up in the list to add, see "My channel isn't showing up to add".
4. Is the channel paused?
Each connected channel has a status badge — ACTIVE (green) or PAUSED (gray). A paused channel keeps the bot connected but stops it from replying there. To turn it back on, open Channels, find the channel in your Connected channels list, and click Resume. The badge should switch to ACTIVE.
5. Has the channel reached its monthly budget?
A channel can have a monthly spending cap. When a channel hits its cap, it stops replying for the rest of the month to protect your budget — this is intentional. It starts replying again automatically at the start of the next month. If you need it back sooner, open Channels and click Resume on that channel. To change the cap itself, reach the Raileon team — the limit isn't editable from the dashboard yet.
6. Is the bot actually in the server or chat?
Your assistant can only reply where the bot has been added:
- Discord: The bot must be invited to your server (guild). If you haven't invited it yet, it can't see any channels there.
- Telegram: The bot must be added to the group, or you must have started a direct chat with it.
If you connected a bot but no channels appear to add, this is the usual cause.
My channel isn't showing up to add
After you connect a bot, Raileon shows the channels that bot can serve. If your channel is missing:
On Discord:
- Make sure the bot has actually been invited to your server. Raileon can only see servers the bot has joined. You invite a bot from the Discord Developer Portal: open your application, go to OAuth2 → URL Generator, tick the bot scope, then under Bot Permissions tick at least View Channels, Send Messages, and Read Message History. Open the generated URL in your browser and choose the server to add the bot to.
- Only text channels and announcement channels appear. Voice channels and other channel types are not supported and won't be listed.
- Make sure the bot's role isn't blocked from viewing the channel. If the bot can't see a channel, that channel won't appear.
On Telegram:
- Add the bot to your group and then send a message in that group. Telegram only reveals a chat to Raileon once the bot has actually seen activity there — if the bot was added but nobody has posted since, the chat won't appear yet. Send a message and try again.
- For a one-to-one chat, message the bot directly first, then re-check.
After fixing any of the above, return to the Channels page and look again under Channels [platform] can serve.
Why does it only reply when I mention it?
This depends on the platform, and it's by design in this first version:
- Discord channels: The assistant replies only when you @mention it. This keeps it from jumping into every conversation in a busy channel. To get a reply without mentioning it, send the bot a direct message — in DMs it replies to everything.
- Telegram: The assistant replies to every message in a group it's a member of, and to every message in a one-to-one chat. There is no mention requirement on Telegram.
In all cases, the assistant never replies to other bots, and it ignores empty messages.
I get an "invalid token" error when connecting
When you paste a token and click Connect, Raileon checks it with Discord or Telegram before saving. If you see an "invalid or unauthorized bot token" message, it means the platform didn't recognise the token. Common causes:
- The token was copied incompletely, or has an extra space at the start or end.
- The token was reset or regenerated on the platform after you copied it. In Discord, clicking Reset Token on the Bot page invalidates the old one; on Telegram, sending BotFather the /token command (or /revoke) issues a new one. After either, copy the new token and use that.
- You pasted a Discord token while Telegram was selected, or vice versa. Make sure the Platform dropdown matches the bot.
Fix the token, paste it again, and click Connect. There's no separate "expiry" to worry about — a token works until you reset it on the platform.
If instead you see a message about not being able to reach Discord or Telegram, that's a temporary connection problem between Raileon and the platform — wait a moment and try again.
Where do the bot's replies appear?
Replies appear in the same place the message came from:
- A message in a Discord channel gets a reply in that channel.
- A direct message to the bot gets a reply in that DM.
- A message in a Telegram group gets a reply in that group; a one-to-one message gets a reply in that chat.
The assistant does not move conversations elsewhere or email you replies — it answers right where your customers and team already are. On Telegram, you'll see a "typing" indicator while the assistant is working on its answer.
Very long replies are handled automatically. On Discord, a long answer is split into several messages so it fits Discord's message size limit; on Telegram it's sent as a single message.
Is my data private? Who can see my conversations?
Your data stays yours:
- Your bot's token is envelope-encrypted and stored separately for your workspace alone. It is never shared with other customers.
- Each workspace is fully isolated — your conversations are never mixed with anyone else's.
- See Security and your data for more on how Raileon protects your information.
Will my customers know what powers the assistant?
No. The assistant always speaks under your brand, using your name, your avatar, and your voice. Raileon automatically removes any mention of the underlying technology from replies before they're sent, so your customers only ever see your brand — never the technology behind it.
What's supported in this first version?
To set expectations, here's exactly what this first release does and doesn't do.
Supported now:
- Connecting a Discord or Telegram bot with its token.
- Discovering and adding the channels your bot can serve.
- Discord: replies in direct messages, and replies in channels when the bot is @mentioned.
- Telegram: replies to every message in groups the bot is in, and in one-to-one chats.
- Marking each channel for your team (Staff).
- Pausing and resuming any connected channel from the dashboard.
- A typing indicator on Telegram while the assistant works.
Not available yet:
- Full customer-facing channels. You'll see a "Customer (coming soon)" option when adding a channel. You can select it and it will reply, but it's an early preview with fewer safety controls and the agent can't post into customer channels on its own — so we recommend Staff for every channel for now.
- Discord replying to every message in a channel without an @mention.
- Slash commands and buttons on Discord, and inline keyboards on Telegram.
- Live-updating ("streaming") replies that fill in as the assistant types.
- A typing indicator on Discord (it's available on Telegram only for now).
- An approval queue for channels that require staff sign-off before the assistant acts.
We'll keep this list current as more of these arrive.
Still stuck?
If you've worked through this page and your bot still isn't behaving as you expect, reach the Raileon team — tell us which platform you're on and what you're seeing, and we'll help you get it running.