Dialogs
EnableX Dialogs is a conversational AI platform for building chatbots and voicebots — flow-based or generative-AI driven — that reach users across every channel they already use. This section documents how to build your own custom client that talks directly to the Dialogs bot engine, for cases where the pre-built widgets don't fit your product.
Dialogs ships default, ready-to-embed widgets (Web Chat Widget, etc.) that you configure from the EnableX Portal with no code — see the Dialogs product page for that. This developer documentation covers the opposite case: writing your own web chat UI, web voice UI, or mobile app voice UI that talks to the same backend over open REST/WebSocket APIs. Portal configuration and no-code bot building are not covered here.
Omni-Channel, One Bot Engine
A single Dialogs bot can be reached through multiple channels. Custom-client development is currently documented for the channels marked below; the rest are available today only through EnableX's pre-built widgets.
| Category | Channel | How users reach it / Custom client docs |
|---|---|---|
| Chatbot | Web Chat | Custom client docs available |
| Users chat via the WhatsApp app | ||
| RCS | Users chat via their RCS-enabled messaging app | |
| Facebook Messenger | Users chat via Facebook Messenger | |
| Users chat via Instagram Direct | ||
| Voicebot | Web Voice | Custom client docs coming soon |
| Mobile App Voice | Custom client docs coming soon | |
| PSTN | Users call in via phone | |
| WhatsApp Voice | Users call via the WhatsApp app |
Build Your Own Client
Connect a custom web chat UI to the Dialogs bot engine over REST + Socket.IO. Covers session/identity, every REST endpoint, realtime events, agent handoff, and click-to-call, plus SDKs and UI Kits for every platform.
Connect a custom web or mobile app voice client to the Dialogs voice bot engine — for the web via the Voicebot SDK, and for native mobile apps via the Android, iOS, React Native, and Flutter SDKs and UI Kits.
Architecture at a Glance
Both Chat Bots and Voice Bots follow the same integration shape: your client opens a realtime connection (Socket.IO for chat) to a guest-style session, receives a session id, and then uses that session id on every subsequent REST call. Bot replies and status events flow back over the same realtime connection. See Chat Bots for the fully worked example.