Bot Version
A Bot Version in Salesforce Einstein Bots represents a specific iteration of a bot's configuration.
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.
In plain English
“A Bot Version is a specific saved copy of an Einstein Bot's configuration. Each time you change how the bot works, those changes are tracked as part of the current version, and you can save a new version when you're ready to make bigger changes. Only one version can be live at a time.”
Worked example
Caraway Spices' Einstein Bot is at Bot Version 4 - version 1 was the initial build, version 2 added two new dialogs, version 3 added Spanish-language support, version 4 (the active one) added a hand-off-to-agent improvement. The team is now developing version 5 with new product-recommendation logic; they save it as a separate version, leaving version 4 active while testing version 5 internally. Once they're confident, they activate version 5 - which automatically deactivates version 4 - and the new logic goes live for customers. If something breaks, they can re-activate version 4 in seconds. Bot Versions are the platform's way to support iterative development without breaking the live experience.
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
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.
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.
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.
Trust & references
Straight from the source - Salesforce's reference material on Bot Version.
- Chat with Customers with Einstein BotsSalesforce Help
Test your knowledge
Q1. How many versions of a bot can be active at one time?
Q2. What is a key benefit of Bot Versions?
Q3. What happens to previous versions when you activate a new one?
Discussion
Loading discussion…