Skip to main content
Share
Guides

Discord Message Content Intent: What It Gates, How to Enable It, and Fixing 4014

Without the Message Content intent your bot still gets every message event, but content, embeds and attachments arrive empty. Here is what the intent gates, the exceptions, how to enable it in the portal and in discord.js or discord.py, the June 2026 switch from 100 servers to 10,000 users, and close code 4014.

Content & Engineering
Oct 14, 2026
16 min read
Updated Nov 2026Last verified November 2026
discord message content intentprivileged intentsmessage content intent not workingdisallowed intents 4014discord gateway 4014
TL;DR

Without the Message Content intent your bot still gets every message event, but content, embeds and attachments arrive empty. Here is what the intent gates, the exceptions, how to enable it in the portal and in discord.js or discord.py, the June 2026 switch from 100 servers to 10,000 users, and close code 4014.

Key Takeaways
  • The Message Content intent is a privileged Gateway intent ( MESSAGE_CONTENT , 1 << 15 ) that lets your Discord bot read the content , embeds , attachments , components and poll fields of messages.
  • Without it, your bot still receives message events, but those fields arrive empty - so prefix commands like !help silently never match.
  • To use it, toggle Message Content Intent on the Bot page of the Developer Portal and request it in your code, then restart the bot.
  • Last verified: November 2026 against Discord's Gateway documentation, the Privileged Intent Review guide and the developer change log.

Start here: what the Message Content intent does

The Message Content intent is a privileged Gateway intent (MESSAGE_CONTENT, 1 << 15) that lets your Discord bot read the content, embeds, attachments, components and poll fields of messages. Without it, your bot still receives message events, but those fields arrive empty - so prefix commands like !help silently never match. To use it, toggle Message Content Intent on the Bot page of the Developer Portal and request it in your code, then restart the bot.

Last verified: November 2026 against Discord's Gateway documentation, the Privileged Intent Review guide and the developer change log.

Two facts trip up most developers. First, it is not tied to any event: per Discord's Gateway docs, it "isn't directly associated with any Gateway events. Instead, access to MESSAGE_CONTENT permits your app to receive message content data across the APIs." That includes REST responses, not just the Gateway. Second, missing it does not produce an error. Your bot connects, shows online, receives MESSAGE_CREATE, and reads an empty string.

SituationWhat you observe
Intent off in portal, not requested in codeBot online; message.content is "" in servers
Intent requested in code, off in portalConnection closed with 4014 Disallowed intent(s)
Intent on in portal, not requested in codeBot online; content still empty
On in portal and requested in codeContent populated

What changed in 2026: 10,000 users replaces the 100-server rule

Most guides still say you can toggle privileged intents freely until your bot reaches 100 servers. That stopped being true on June 10, 2026. Discord's change log and the Privileged Intent Review guide describe the new rules:

  • The review threshold is users, not servers. If your app is accessible to fewer than 10,000 unique users across all its servers, you can turn privileged intents on and off in the Developer Portal with no application. Once it passes 10,000 users, you must apply for access. Discord's own example: a bot in 50 large servers can hit the threshold while a bot in 200 small servers may not.
  • A 90-day window. When an app crosses the threshold with a privileged intent enabled, the owner is notified (system DM and/or email, plus a callout in the portal) and has 90 days to apply. Miss the window and existing access is removed, though you can apply again any time.
  • Annual reapplication. Apps already granted access must reapply once a year, again with a 90-day window after the notice.
  • Bots keep working during review. An app under review continues to use the intents it requested and can keep joining servers.
  • Verification and intent review are now separate processes. The Gateway docs still describe verification as "required for apps in 100+ guilds", but it no longer doubles as your intent review.

Practical meaning: a small bot does not need permission from anyone, but you should still build with the minimum set of intents, because growth later forces you to justify each one in writing.

When you get content without the intent

The intent is not needed in several situations, which is why a bot can "work in DMs but not in the server" or "respond when pinged but ignore everything else". Discord's docs list these exceptions:

  • Messages your app sends.
  • Direct messages sent to your app.
  • Messages that @mention your app.
  • The target message of a message context menu command (right-click a message, Apps, your command).
  • Replies to your app's messages made with Discord's reply feature with "ping on reply" enabled. Discord's You Might Not Need a Privileged Intent guide notes this does not apply to replies to slash command responses.

If your feature can be designed around those - mention the bot, DM the bot, or use a context menu - you do not need the intent at all. That is not a workaround; it is what Discord explicitly recommends: "If your app's functionality can be built to work with this access, you should not request the Message Content intent."

Note what the intent does not gate: it does not stop you receiving MESSAGE_CREATE (that is GUILD_MESSAGES and DIRECT_MESSAGES), and it does not affect message IDs, authors, timestamps or channel IDs. A bot that only needs to know that someone posted - activity counters, XP systems based on message count - works without it.

Try it yourself
Build your first chatbot free
Free plan, no credit card required. Live on your site in about 10 minutes.
Start building free

Enabling it in the Developer Portal

  1. Open discord.com/developers/applications and select your app.
  2. Go to the Bot page in the left sidebar.
  3. Scroll to Privileged Gateway Intents.
  4. Toggle Message Content Intent on and save the change.
  5. Restart the bot. Discord's review guide is explicit: intent changes only take effect on a new Gateway connection, so a running bot will not pick them up until it reconnects.

If the toggle is locked, your app is over the 10,000-user threshold and needs approved access; apply from the same page. The other two privileged intents live in the same section: Presence Intent (GUILD_PRESENCES) and Server Members Intent (GUILD_MEMBERS). Do not enable them "just in case" - each one is something you will have to justify if the bot grows.

Requesting it in code: discord.js, discord.py and raw Gateway

Since Gateway API v8, every intent you want must be listed when you identify. The portal toggle grants permission; your code has to ask for it.

discord.js (v14)

import { Client, GatewayIntentBits, Events } from "discord.js";

const client = new Client({
  intents: [
    GatewayIntentBits.Guilds,
    GatewayIntentBits.GuildMessages,     // receive MESSAGE_CREATE in servers
    GatewayIntentBits.MessageContent,    // privileged: populate message.content
  ],
});

client.on(Events.MessageCreate, (msg) => {
  if (msg.author.bot) return;
  if (msg.content === "!ping") msg.reply("pong");
});

client.login(process.env.DISCORD_TOKEN);

MessageContent without GuildMessages is a common half-fix: you are allowed to read content, but you never receive the server messages that would contain it. Add GatewayIntentBits.DirectMessages (and the Partials.Channel partial) if you also handle DMs.

discord.py (2.x)

import os, discord
from discord.ext import commands

intents = discord.Intents.default()
intents.message_content = True          # privileged

bot = commands.Bot(command_prefix="!", intents=intents)

@bot.command()
async def ping(ctx):
    await ctx.send("pong")

bot.run(os.environ["DISCORD_TOKEN"])

Intents.default() deliberately leaves out the privileged intents, so prefix commands in commands.Bot do nothing in servers until you set message_content = True.

Raw Gateway identify

If you speak to the Gateway directly, add the bit to your intents integer. GUILDS (1 << 0) + GUILD_MESSAGES (1 << 9) + MESSAGE_CONTENT (1 << 15) = 1 + 512 + 32768 = 33281:

{
  "op": 2,
  "d": {
    "token": "YOUR_BOT_TOKEN",
    "intents": 33281,
    "properties": { "os": "linux", "browser": "my_bot", "device": "my_bot" }
  }
}

A wrongly calculated value that includes undefined bits closes the connection with 4013 Invalid intent(s), which is different from 4014.

Try the free chatbot builder
600 conversations a month, every channel, no credit card.
Start free

Requesting it in Go, Java, C# and Rust

Every major library starts from a non-privileged default and expects you to add Message Content explicitly. That is the safe choice, and it is why "I enabled the toggle and nothing changed" is so common. Code that never asks for the intent still gets empty content.

LibraryDefault intentsHow to add Message Content
discord.jsNone - you must list every intentGatewayIntentBits.MessageContent
discord.pyIntents.default() leaves out privileged intentsintents.message_content = True
discordgoIntentsAllWithoutPrivileged, set in New()discordgo.IntentMessageContent
JDAcreateDefault disables GUILD_MEMBERS, GUILD_PRESENCES and MESSAGE_CONTENT.enableIntents(GatewayIntent.MESSAGE_CONTENT)
Discord.NetGatewayIntents.AllUnprivileged excludes itGatewayIntents.MessageContent
serenityGatewayIntents::non_privileged() excludes itGatewayIntents::MESSAGE_CONTENT

Go (discordgo)

dg, _ := discordgo.New("Bot " + os.Getenv("DISCORD_TOKEN"))
dg.Identify.Intents = discordgo.IntentsGuilds |
    discordgo.IntentsGuildMessages |
    discordgo.IntentMessageContent // privileged

dg.AddHandler(func(s *discordgo.Session, m *discordgo.MessageCreate) {
    if m.Author.Bot {
        return
    }
    if m.Content == "!ping" {
        s.ChannelMessageSend(m.ChannelID, "pong")
    }
})
dg.Open()

Java (JDA)

JDA jda = JDABuilder.createDefault(System.getenv("DISCORD_TOKEN"))
    .enableIntents(GatewayIntent.MESSAGE_CONTENT)   // privileged
    .addEventListeners(new PingListener())
    .build();

C# (Discord.Net)

var client = new DiscordSocketClient(new DiscordSocketConfig
{
    GatewayIntents = GatewayIntents.AllUnprivileged | GatewayIntents.MessageContent
});

Rust (serenity)

let intents = GatewayIntents::non_privileged() | GatewayIntents::MESSAGE_CONTENT;
let mut client = Client::builder(&token, intents).event_handler(Handler).await?;

Whichever library you use, the portal toggle still has to be on for the same application whose token you load. Our guide to getting a Discord bot token covers the dev-versus-production application split that causes most "wrong app" 4014s.

Every Gateway intent and its bit value

If you build the identify payload yourself, or just want to check what a number in someone's config means, this is the full list from Discord's Gateway documentation. The three privileged intents are marked.

IntentBitValueNotable events
GUILDS1 << 01GUILD_CREATE, channel, role and thread events
GUILD_MEMBERS (privileged)1 << 12GUILD_MEMBER_ADD / UPDATE / REMOVE
GUILD_MODERATION1 << 24Bans, audit log entries
GUILD_EXPRESSIONS1 << 38Emoji, sticker and soundboard updates
GUILD_INTEGRATIONS1 << 416Integration events
GUILD_WEBHOOKS1 << 532WEBHOOKS_UPDATE
GUILD_INVITES1 << 664INVITE_CREATE / DELETE
GUILD_VOICE_STATES1 << 7128VOICE_STATE_UPDATE
GUILD_PRESENCES (privileged)1 << 8256PRESENCE_UPDATE
GUILD_MESSAGES1 << 9512MESSAGE_CREATE / UPDATE / DELETE in servers
GUILD_MESSAGE_REACTIONS1 << 101024Reaction add / remove
GUILD_MESSAGE_TYPING1 << 112048TYPING_START
DIRECT_MESSAGES1 << 124096MESSAGE_CREATE in DMs
DIRECT_MESSAGE_REACTIONS1 << 138192Reactions in DMs
DIRECT_MESSAGE_TYPING1 << 1416384Typing in DMs
MESSAGE_CONTENT (privileged)1 << 1532768No events of its own - fills content fields
GUILD_SCHEDULED_EVENTS1 << 1665536Scheduled event create / update / delete
AUTO_MODERATION_CONFIGURATION1 << 201048576AutoMod rule changes
AUTO_MODERATION_EXECUTION1 << 212097152AUTO_MODERATION_ACTION_EXECUTION
GUILD_MESSAGE_POLLS1 << 2416777216Poll votes in servers
DIRECT_MESSAGE_POLLS1 << 2533554432Poll votes in DMs

Common combinations

Bot typeIntentsValue
Prefix-command bot in serversGUILDS + GUILD_MESSAGES + MESSAGE_CONTENT33281
Same, also answering DMs+ DIRECT_MESSAGES37377
Slash-command-only botGUILDS1
Bot that counts messages but never reads themGUILDS + GUILD_MESSAGES + DIRECT_MESSAGES4609

A value with bits Discord does not define closes the connection with 4013. A valid value that includes a privileged bit you have not enabled closes it with 4014. Gateway connections are long-lived WebSockets, so you only find out at identify time, which is another reason to log close codes rather than swallow them.

Close code 4014: Disallowed intent(s)

Discord's close code table defines 4014 as: "You sent a disallowed intent for a Gateway Intent. You may have tried to specify an intent that you have not enabled or are not approved for." It is marked as not reconnectable - retrying the same identify will fail the same way, so libraries stop and raise. What each library prints:

LibraryWhat you see
discord.js / @discordjs/wsError: Used disallowed intents
discord.pydiscord.errors.PrivilegedIntentsRequired: Shard ID None is requesting privileged intents that have not been explicitly enabled in the developer portal...
Raw WebSocketClose frame with code 4014 right after identify

The fix is always one of three:

  1. Toggle is off. Turn on the matching intent on the Bot page. Check all three privileged intents, not just Message Content - requesting GuildMembers or GuildPresences without the toggle triggers the same code.
  2. Wrong application. The token in your environment belongs to a different app (often a dev copy) than the one you toggled.
  3. Access removed or not granted. Over the 10,000-user threshold, without approved access, or past a missed 90-day window. Apply in the portal, or remove the intent from your code.

The reverse mismatch - enabled in the portal, not requested in code - never errors. It just leaves content empty, which is why "my bot is online and ignores commands" is the more common report. Our Discord bot not responding guide covers the other causes of a silent bot once intents are ruled out.

The other two privileged intents: Server Members and Presence

Message Content gets the attention, but the review applies to all three privileged intents. Discord's guide You Might Not Need a Privileged Intent lists what each one unlocks and what works without it:

IntentWhat it unlocksWhat works without it
Server Members (GUILD_MEMBERS)Join, update and leave events; the full member list via Request Guild Members or List Guild MembersGet Guild Member by ID, Search Guild Members by name prefix, and the member object included in every interaction payload
Presence (GUILD_PRESENCES)PRESENCE_UPDATE: online status, activities and client platformapproximate_presence_count on the guild object, Get User for profiles, and setting your own bot's status

Two side effects are easy to miss. First, without GUILD_PRESENCES (or in servers over 75,000 members), the members and presences arrays in GUILD_CREATE contain only your bot and users in voice channels. Code that builds a member cache from that event silently ends up with a near-empty cache. Second, requesting a server's entire member list over the Gateway needs GUILD_MEMBERS; a prefix query still works without it but returns at most 100 members.

The most common legitimate need for Server Members is a welcome message: to post something when someone joins, a bot has to receive GUILD_MEMBER_ADD, and only that intent delivers it. Discord's review guide lists "My welcome messages stopped firing" as a standard symptom. If you only need to look up the member who just ran a command, you already have them in the interaction - no intent required. For moderation features, check first whether Discord's built-in AutoMod covers them: AutoMod blocks show up to bots as 200000, and the review guide calls replicating AutoMod "generally not considered a compelling use case for access."

REST responses, and writing an intent application that gets approved

The intent applies to REST too

Developers often assume that if the Gateway hides content, fetching the message over HTTP will reveal it. It will not. Discord's Gateway docs state that privileged intents also affect the HTTP API, and that those HTTP restrictions are "independent of Gateway restrictions, and are unaffected by which intents your app passes in the intents parameter". In other words, for REST the portal toggle (and approval, if you are over the threshold) is what counts. Fetching channel history without access gives you message objects with empty content fields, and some endpoints require the intent outright: the Search Guild Messages endpoint Discord documented in March 2026 needs both the READ_MESSAGE_HISTORY permission and MESSAGE_CONTENT.

If you have to apply

Over 10,000 users, access is a written application. Discord's review guide is direct about what gets denied: requests that do not show the use case requires access (for example, because it could be built with interactions), and submissions that are unclear or incomplete. Its advice, condensed:

  • Be specific. "My bot needs message content" is not a justification; describe the feature, what data it reads and why a slash command, context menu or modal cannot replace it.
  • Request only what you use. Asking for Presence or Server Members alongside Message Content without a matching feature hurts the submission.
  • Explain data handling. Say whether you store message content, for how long and how it is secured - or that you process it in memory and discard it.
  • Show it working. Discord suggests including evidence such as screenshots or video of the feature.
  • Plan for the annual renewal. Keep the write-up somewhere you can update; you will resubmit it every year.

For moderation bots, Discord adds a pointed check: does the feature go beyond what the AutoMod API already supports? Replicating AutoMod is "generally not considered a compelling use case for access."

The alternative Discord wants you to use: slash commands

Discord's review guide calls text-to-slash migration "the most common reason developers request the Message Content privileged intent" and recommends slash commands as the replacement. They need no privileged intent at all, and they bring things a prefix parser never had:

NeedPrefix command + Message ContentInteraction-based alternative
Run a command with argumentsParse !cmd arg from contentSlash command with typed options (string, integer, user, channel, role, attachment...)
Act on a specific message (translate, report, save)Read every messageMessage context menu command - you receive the target message's content
Collect free text from a userWait for their next messageModal with text inputs
Let users pick from choicesReact or type a numberButtons or select menus

Slash commands also handle discovery (users see them in the / picker), argument validation and autocomplete. Keep Message Content only when the feature genuinely requires reading free-form conversation - for example AI assistants that join a channel conversation or moderation beyond what AutoMod covers - and write down why, because over 10,000 users that explanation becomes your application.

If you are building a support or FAQ bot and would rather not run Gateway code at all, Conferbot's Discord integration handles the connection side so you can design the conversation instead.

Debug checklist for empty message content

  1. Log message.content length and message.guild. Empty only in servers, but fine in DMs or when mentioned? It is the intent.
  2. Check the Bot page: Message Content Intent toggled on for this application ID.
  3. Check your client constructor: MessageContent / message_content plus GuildMessages requested.
  4. Restart the process after any portal change.
  5. If the connection closes immediately, read the close code: 4014 means a privileged intent mismatch, 4013 a malformed bitfield, 4004 a bad token.
  6. If content arrives but the bot still cannot answer, it is permissions: see 50013 Missing Permissions and check channel overwrites with the permissions calculator.

Every code mentioned here has its own page in the Discord error code directory, and platform quotas are summarized on the Discord limits page.

Running Discord as a support or sales channel, not just a community server

Support bots are the case where Discord's preferred alternatives fit least. A member with a problem types a sentence into a help channel; they do not type a slash command with typed options. You can design around that - ask members to mention the bot, open a DM, or start from a button - and Discord recommends exactly that where it works. If the bot has to answer free-form questions in a channel without being mentioned, though, that is reading conversation, and it needs Message Content.

Designing a support bot that keeps the intent narrow

  • Use DMs and mentions where you can. Both are explicit exceptions, so a bot that answers DMs and @mentions needs no privileged intent at all.
  • Use a dedicated help channel if you need the intent, and say so in your application. "Reads messages in #support to answer product questions and hand off to staff" is a specific, reviewable use case.
  • Process, don't store. If you only need a message long enough to answer it, say that you process content in memory and discard it - Discord's review guide asks about retention directly.
  • Treat content as untrusted input if an AI model reads it. A bot that pastes channel messages into an LLM prompt can be steered by those messages; our guide to prompt injection covers the defenses.
  • Plan the handoff. A support bot that cannot answer should pass the member to a person. Our human handoff guide covers when and how.

Discord support bots fit some audiences better than others: education servers running cohorts, creator and media communities, developer communities and nonprofit volunteer hubs. For the community side - roles, onboarding and moderation - see Discord bot community management.

Where Conferbot fits

Conferbot's Discord integration is this kind of bot. It reads what members type and answers with messages and buttons in DMs, replies or threads, so its setup has you turn on Message Content Intent for your application, as described above. Under 10,000 users that is a toggle; above it, you apply with your support use case like any other app. What you skip is the code: Conferbot keeps the Gateway connection and intents in sync, so a toggle mismatch never becomes a 4014 crash loop. Conversations can hand off to live chat, and on Pro and up they can push data out through the integrations hub. It does not register slash commands and is not a moderation bot.

When to stop maintaining the plumbing

Everything in this guide is transport-layer work: which bits to send, which toggles to flip, which library default left content empty, which close code means what, and what to write in an application you will resubmit every year. None of it is your product. Every platform charges its own version of this toll - our guides to Slack bots not responding and Telegram bots not responding exist because the same "online but silent" problem has a different cause on each one.

That is a fair trade for a community bot you enjoy building. It is a worse one when Discord is a support or sales channel, and worse again when it is one of several. Conferbot runs the same flow on Telegram, WhatsApp, Slack and a website widget, and you can try it on the free plan before deciding.

Start free with Conferbot - the free plan includes 600 conversations a month and needs no credit card, so you can have the same flow running on a second channel this afternoon.

If you are debugging today, work the checklist above: empty content in servers but not in DMs is the intent, every time. If the bot still will not post, see the invite link guide for permissions, or 50001 Missing Access for channel visibility. If the bot only needs to post into a channel and never read it, a webhook needs no intent at all.

Share this article:

Was this article helpful?

Ready to build your chatbot?

Join the businesses. Deploy on website, WhatsApp, and 11 more channels in minutes. Free forever plan available.

No credit cardNo coding13+ channels
Start Building Free

Get chatbot insights delivered weekly

Join 5,000+ professionals getting actionable AI chatbot strategies, industry benchmarks, and product updates.

🎯Automate this with a free chatbot

Build and deploy in 10 minutes. No coding needed.

❓FAQ

Discord Message Content Intent FAQ

Everything you need to know about chatbots for discord message content intent.

🔍
Popular:

It is a privileged Gateway intent, MESSAGE_CONTENT with bit value 1 << 15, that allows your app to receive the content, embeds, attachments, components and poll fields of messages across the Gateway and REST API. Without it those fields come back empty, except in DMs to your bot, messages that mention it, its own messages and a few other documented exceptions.

Your bot either has not enabled Message Content Intent on the Bot page of the Developer Portal, or has not requested it in code, or both. Both are required, and the process must restart afterwards. In discord.js add GatewayIntentBits.MessageContent alongside GuildMessages; in discord.py set intents.message_content = True before creating the client.

4014 is Disallowed intent(s): your identify payload requested a privileged intent that is not enabled for the application in the Developer Portal or not approved for it. discord.js reports it as Used disallowed intents and discord.py raises PrivilegedIntentsRequired. Enable the intent on the Bot page, confirm the token belongs to that same application, or stop requesting the intent.

Not under the current rules. Since June 10, 2026, Discord bases privileged intent review on users rather than servers. Apps accessible to fewer than 10,000 unique users can toggle privileged intents freely in the portal. Above that threshold you must apply for access and reapply annually. App verification is now a separate process from privileged intent review.

No. The old rule, where apps in 100 or more servers needed approval for privileged intents, was replaced on June 10, 2026 by a 10,000 unique user threshold. Discord's docs still describe app verification as required for apps in 100 or more servers, but verification is now a separate process and no longer the trigger for intent review.

Yes. Discord's documentation lists messages that mention your app as an exception, along with direct messages to your app, messages your app sends, the target message of a message context menu command, and replies to your app's regular messages when ping on reply is enabled. Designing features around mentions or context menus can remove the need for the intent.

No. Slash commands, message context menu commands, buttons, select menus and modals are interactions, and none of them require a privileged intent. Discord recommends migrating prefix commands to slash commands as the main alternative to requesting Message Content. Slash commands also give you typed options, validation, autocomplete and discoverability in the command picker.

Yes. Intents are negotiated when the bot identifies on a new Gateway connection, so a running process will not pick up a portal change until it reconnects. Toggle the intent, make sure your code requests it, then fully restart the process. If the connection then closes with 4014, the portal toggle and your code still disagree.

Discord notifies the app or team owner by system DM and/or email and shows a callout in the Developer Portal. You then have 90 days to apply for privileged intent access, and the bot keeps working while the request is under review. If you do not apply in time, access is removed, though you can submit a new request later.

GUILD_MEMBERS (Server Members Intent), GUILD_PRESENCES (Presence Intent) and MESSAGE_CONTENT (Message Content Intent). Server Members unlocks join, update and leave events and full member lists. Presence unlocks status and activity updates. Message Content fills the content, embeds, attachments, components and poll fields of messages. All three are toggled on the Bot page and reviewed above 10,000 users.

GUILDS (1) plus GUILD_MESSAGES (512) plus MESSAGE_CONTENT (32768) adds up to 33281, enough to receive and read messages in servers. Add DIRECT_MESSAGES (4096), for 37377, if the bot also answers DMs. A bot that only uses slash commands can identify with GUILDS (1) alone, because interactions do not depend on message intents.

No mainstream library does. discord.js makes you list every intent, discord.py's Intents.default() leaves out privileged intents, discordgo defaults to IntentsAllWithoutPrivileged, JDA's createDefault disables Message Content, and Discord.Net's AllUnprivileged and serenity's non_privileged() exclude it. Enabling the portal toggle without changing your code still leaves content empty.

About the Author

Content & Engineering

The Conferbot team writes about building, deploying, and improving AI chatbots.

View all articles
Skip the blank canvas
Start from one of 250+ free chatbot templates for lead generation, support, e-commerce, and 20+ industries - customize and launch in minutes.
Browse free templates

Related Articles

From the reference shelf

Fact-checked reference pages and free tools for the platform this article covers.

Omnichannel Platform

One Chatbot,
Every Channel

Your chatbot works seamlessly across WhatsApp, Messenger, Slack, and 6 more platforms. Build once, deploy everywhere.

View All Channels
Conferbot
online
Hi! How can I help you today?
I need pricing info
Conferbot
Active now
Welcome! What are you looking for?
Book a demo
Sure! Pick a time slot:
#support
Conferbot
New ticket from Sarah: "Can't access dashboard"
Auto-resolved. Password reset link sent.