Bot Connector vs Digital Bot Connector
Genesys Cloud offers two distinct mechanisms for integrating third-party bots: the original Bot Connector (commonly called v1) and the newer Digital Bot Connector (v2). Understanding their differences is critical for choosing the right integration path.
Bot Connector (v1): The Original
The Bot Connector was the first mechanism Genesys provided for third-party bot integration. It was designed primarily for voice and IVR (Interactive Voice Response) workflows and uses a synchronous request-response architecture.
Key characteristics:
- • Synchronous architecture — Genesys sends a request to your bot and expects the response in the same HTTP connection. There is no callback mechanism.
- • 11-second timeout limit — Your bot must respond within approximately 11 seconds or the request fails. This is a hard limitation of the synchronous architecture.
- • Primarily for voice/IVR flows — Designed to work with Architect call flows using the Call Bot Connector action.
- • Up to 5 integrations — Genesys limits each organization to a maximum of 5 third-party bot connector integrations.
- • Text-only responses — Limited support for rich media; primarily plain text and simple slot/intent data.
The 11-second timeout is the single biggest limitation of Bot Connector v1. Modern LLM-powered bots (using GPT-4, Claude, Gemini, or similar models) routinely need 5–30 seconds to generate a response, making the v1 connector unreliable or outright unusable for AI-powered use cases.
Digital Bot Connector (v2): The Next Generation
The Digital Bot Connector is a fundamentally different API designed from the ground up for digital messaging channels. It uses an asynchronous architecture that removes the timeout constraints of v1 and adds rich media support.
Key characteristics:
- • Asynchronous, distributed architecture — Genesys sends a message to your bot, and your bot responds via a separate callback. No tight coupling to a single HTTP connection.
- • Extended timeouts (20–60+ seconds) — Built for LLM bots and complex AI processing that need more time to generate high-quality responses.
- • Designed for digital channels — Web messaging, SMS, WhatsApp, and Facebook Messenger. Uses the Call Digital Bot Connector action in Architect message flows.
- • Rich media support — Cards, carousels, quick reply buttons, images, and structured content — not just plain text.
- • Full session lifecycle — Explicit events for session start, message exchange, session end, and agent transfer.
Side-by-Side Comparison
| Feature | Bot Connector (v1) | Digital Bot Connector (v2) |
|---|---|---|
| Architecture | Synchronous | Asynchronous (callback-based) |
| Timeout | ~11 seconds | 20–60+ seconds |
| Primary channels | Voice / IVR | Web chat, SMS, WhatsApp, Messenger |
| Architect action | Call Bot Connector | Call Digital Bot Connector |
| Architect flow type | Call flows | Message flows |
| Rich media | Limited (text only) | Cards, carousels, quick replies, images |
| LLM-friendly | No (timeout too short) | Yes (async + extended timeouts) |
| Integration limit | Up to 5 | Configurable |
When to Use Which
Use Bot Connector (v1) when:
- • You need to integrate a bot into voice/IVR call flows
- • Your bot can reliably respond within 11 seconds (intent-based bots with fast inference)
- • You only need text-based responses without rich media
Use Digital Bot Connector (v2) when:
- • You are deploying bots on digital channels (web chat, SMS, WhatsApp, Messenger)
- • You are using LLM-powered bots that need longer response times
- • You need rich media: cards, carousels, quick replies, or images
- • You want an asynchronous, more resilient integration architecture
Migration Considerations: v1 to v2
If you are currently using Bot Connector v1 and want to move to Digital Bot Connector v2, keep the following in mind:
- 1 Different Architect flow types. Bot Connector v1 uses call flows with the Call Bot Connector action. Digital Bot Connector v2 uses message flows with the Call Digital Bot Connector action. You will need to create new message flows.
- 2 Different API contracts. The webhook payload structure is different between v1 and v2. Your bot middleware will need to be updated or replaced to handle the new JSON format.
- 3 Async response model. If your current middleware is built for synchronous responses, you will need to adapt it to handle the callback-based async pattern used by v2.
- 4 Channel-specific behavior. Digital channels have different capabilities than voice. Rich media works on web chat and messaging apps, but SMS has limitations on content types.
- 5 Session management changes. v2 has explicit session lifecycle events that may require updating how your bot tracks conversation state.
How ContextQue Supports v2
ContextQue is built exclusively for Digital Bot Connector v2. It handles the async communication model, session management, rich media mapping, and bot platform translation — so you can focus on your bot's conversational logic, not infrastructure plumbing.
If you are migrating from a v1 integration, ContextQue can serve as your new middleware layer, saving you the effort of rebuilding the translation layer from scratch.
Join the waitlist to get started