Five channels. One bot. One knowledge base.

Most chatbot platforms force you to set up a separate bot per channel — one for the website widget, another for WhatsApp, a third for Instagram. You end up maintaining five copies of your knowledge, five sets of behavior toggles, five sets of analytics dashboards. When you update your refund policy, you remember to update it in three places and miss two.

NebulaHex doesn’t work that way. You build one bot, grounded in one knowledge base, with one personality and one set of guardrails. Then you turn on the channels you need. Everything flows through the same brain and into the same inbox, so your team works one queue instead of five.

Knowledge stays consistent. Conversation history stays unified. Analytics stays comparable across channels. And when a conversation escalates to a human, your team picks it up in the unified inbox — whether the customer started on Instagram or WhatsApp or the website widget, the handoff feels the same.

Each channel has its own setup quirks, audience patterns, and behaviour rules. The bot behind them is the same, but the surface area each one offers is different. Pick the one that matches where your customers actually message you today — you can always add more.

Same bot, different surfaces. This is the engineer’s view — everything you need to know about approval requirements, typical use cases, and what kinds of media each channel supports.

The bot you build is the bot that goes live on every channel you connect. There’s no “Telegram edition” or “WhatsApp edition” — you build once and turn on channels as you need them. The free plan gives you the website widget so you can validate everything before you pay for a thing.