Webhooks (calling external APIs) are crucial for order status, CRM lookups, or ticket creation. The updated dialog now supports:
Visual refactoring and real-time validation mean that a conversation designer can build a fully functional dialog in hours instead of days. For agencies or internal teams juggling multiple bot projects, this is a game-changer.
Memory has always been the bottleneck of conversational design. BotX Dialog now supports three distinct scopes of memory variables: botx dialog updated
The Developer Impact: This allows for "nested dialogs." You can build a complex "Returns Process" dialog and nest it inside a "Support" dialog. The variables inside the Returns flow won’t pollute the main Support flow, preventing namespace collisions and making your dialog modules portable.
To quantify the impact, we analyzed five production bots (ranging from 500 to 50,000 monthly conversations) before and after migrating to the updated BotX dialog system. Webhooks (calling external APIs) are crucial for order
| Metric | Before Update | After (BotX Dialog Updated) | | :--- | :--- | :--- | | Average dialog load time | 1.2 seconds | 0.4 seconds | | Unhandled intent rate | 8.7% | 3.2% | | Webhook failure rate | 5.1% | 0.9% (with retries) | | Time to build 20-node dialog | 3 hours | 1 hour | | User satisfaction (CSAT) | 3.2/5 | 4.5/5 |
Source: Internal BotX telemetry, Q2 2025. Memory has always been the bottleneck of conversational
Previously, if a user provided incomplete information (e.g., just a city name instead of full address), the dialog would restart or error out. Now, the updated dialog supports dynamic slot filling – it can ask follow-up questions without losing context.
Example:
User: “Book a flight to Paris.”
Bot: “What date?”
User: “Next Monday.”
Bot remembers “Paris” and “next Monday” without reprocessing the intent.
The BotX dialog updated excels at handling non-linear support scenarios. Consider a retail chatbot helping a customer with a damaged product. The old dialog would rigidly ask: “Order number? → Photos? → Return label?” If the customer asked, “Can I get a refund instead of a replacement?” mid-flow, the bot often crashed or started over.
Now, with BotX dialog updated, the bot recognizes the mid-flow intent change, updates the dialog goal from “replacement” to “refund,” and retains all previously collected information (order number, photos). Customer effort score (CES) drops significantly.