Definition
A Bot Version in Salesforce Einstein Bots represents a specific iteration of a bot's configuration. Each time changes are made to a bot's dialogs, settings, or actions, they are saved as part of the current version. Administrators can activate a version to make it live, deactivate it, or create new versions while preserving previous configurations. Only one version of a bot can be active at a time.
Real-World Example
When a support manager at QuickAssist needs to streamline operations, they turn to Bot Version to improve response times and customer satisfaction scores. After implementing Bot Version, agents have the tools and context they need to resolve issues on the first contact. Average handle time decreases by 20% and CSAT scores climb to an all-time high of 94%.
Why Bot Version Matters
Bot Version is the unit of configuration management for Einstein Bots. Each version is a snapshot of the bot's dialogs, actions, variables, intents, and other settings. Admins can create new versions from existing ones, which lets them make changes to a non-active version without affecting the bot that's currently running in production. Only one version of a bot can be active at a time, so activation is the deliberate step of saying 'this is the version users interact with now'.
Versioning supports a safer development pattern: clone the active version into a new version, make and test changes in the new version, then activate the new version when ready. The previous version is deactivated but preserved, so rolling back means simply activating the earlier version again. This is particularly valuable for bots because conversation logic is complex and mistakes are hard to predict until users start hitting them, and rollback is the fastest fix when a new version causes problems.
How Organizations Use Bot Version
- •QuickAssist — Uses Bot Versions to stage changes: a new version is created and tested each sprint, and only after regression testing is it activated. The previous version stays available for instant rollback if issues surface in production.
- •CloudNine Solutions — Maintains three Bot Versions: the active production version, a staging version for testing the next release, and a development version for early experimentation. This separation mirrors their general code deployment workflow.
- •ShieldGuard Security — Rolled back from Version 12 to Version 11 within 10 minutes of detecting an issue with the new version. Because versioning is a simple activation switch, the rollback was fast and low-risk, which limited customer impact.