Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryEEnhanced Bot
ServiceBeginner

Enhanced Bot

Enhanced Bot is the modern Salesforce Einstein Bot type and the strategic successor to the classic Bot Builder experience.

§ 01

Definition

Enhanced Bot is the modern Salesforce Einstein Bot type and the strategic successor to the classic Bot Builder experience. Introduced in 2022, Enhanced Bots use an improved NLP model, support multi-language conversations within a single bot definition, integrate with Einstein GPT for generative responses, and include Conversation Repair, the auto-detection feature that flags broken conversations and suggests Dialog improvements. New bots default to Enhanced; Classic remains for legacy compatibility but is no longer receiving major features.

The Enhanced Bot Builder UI organizes Dialogs, Topics, Intents, and Entities into a more intuitive structure than Classic. Topics group related Dialogs (Order Management Topic, Account Management Topic). Conversation Repair runs automatically against the bot's conversation logs and identifies utterances the bot failed to handle well, suggesting fixes in the form of new training utterances or Dialog branches. Multi-language support lets one Enhanced Bot handle English, Spanish, French, and other supported languages from a single configuration rather than per-language bot clones.

§ 02

What makes Enhanced Bot different from Classic Bot and worth the migration

Topics and the conversation organization layer

Enhanced Bots organize Dialogs under Topics. A Topic is a logical grouping (Order Management, Account Servicing, Sales Inquiries) that contains multiple related Dialogs. Topics make navigation faster, support modular bot design, and enable reuse: the Authentication Topic with its Identity Dialog can be referenced from multiple other Topics. Classic Bots had no Topics; every Dialog lived in one flat list, which became unmaintainable past 50 Dialogs.

Multi-language conversations in a single bot

Enhanced Bots can detect the customer''s language at conversation start and respond in that language using the same Dialog graph translated per language. Admins maintain one bot configuration; translations are managed via a translation file or inline per-Dialog. Classic Bots required per-language clones, which doubled or tripled maintenance cost. The multi-language improvement is the single biggest reason multinational orgs migrate to Enhanced.

Conversation Repair and the auto-suggest fixes

Conversation Repair scans the bot''s conversation logs daily and flags utterances the bot misclassified or failed to handle. Examples: "track my package" not mapped to the Order Status Intent, "talk to billing" not mapped to the Billing Topic. For each flagged utterance, Conversation Repair suggests an action: add to an existing Intent''s training set, create a new Intent, route to a different Topic. Admins review the suggestions weekly and accept the useful ones. This is the difference between a bot that improves and one that stagnates.

Einstein GPT integration for generative responses

Enhanced Bots can call Einstein GPT for generative responses in two ways. Bot Building Generative Responses lets admins generate Dialog response text from a prompt instead of writing it by hand. Customer-facing GPT generates dynamic responses to customer questions that fall outside the predefined Dialog graph, grounded on the org''s Knowledge articles and CRM data. The GPT integration is opt-in per Dialog or per bot; defaulting to GPT for everything is a recipe for hallucination on sensitive use cases.

Improved NLP model and ambiguity handling

The NLP engine under Enhanced Bots is meaningfully better at handling ambiguous utterances ("I have a problem with my account" maps cleanly to the Account Topic). The model also handles small-talk, follow-up questions, and clarification turns more naturally. Classic''s NLP was rule-leaning and brittle on edge cases. The Enhanced NLP is closer to general-purpose LLM behaviour, which is what customers expect from chatbots in 2025.

Migration from Classic Bot

There is no automatic migration. A Classic Bot must be rebuilt as an Enhanced Bot, reusing the Dialog logic but reconfiguring through the new UI. Salesforce documents a recommended migration approach: snapshot the Classic Bot''s Dialog graph, recreate Topics in Enhanced, redefine Intents and Entities, retrain on existing utterance data, test against historical conversations, then activate the Enhanced version. Plan a sprint for migration; it is not a one-click conversion.

Channel parity and what is supported

Enhanced Bots support the same channels as Classic (Web Chat, Messaging, WhatsApp, Facebook Messenger). However, some advanced channel features ship to Enhanced first (Apple Business Chat rich messages, WhatsApp List Messages). For orgs using cutting-edge channel features, Enhanced is the only option. For orgs on basic Web Chat only, Classic still works but lacks Enhanced''s NLP and Repair improvements.

§ 03

Creating and operating an Enhanced Bot

Enhanced Bot setup uses the same Bot Builder UI shell as Classic but with the Enhanced template selected at creation. The configuration steps mirror Classic with the added Topics layer and multi-language support.

  1. Create a new Enhanced Bot

    Setup, Einstein Bots, New Bot. Pick Enhanced Bot Builder. Configure name, language(s), and channels. The bot starts with a default Topic structure (Welcome, End Conversation, Transfer to Agent).

  2. Build Topics and group Dialogs

    Create a Topic per business area: Order Management, Account Servicing, Billing. Add Dialogs under each Topic. Topics are visible to the customer as conversation starters; a Welcome Dialog can list "I want to ask about ..." options that map to Topics.

  3. Configure multi-language

    Bot Settings, Languages. Add each supported language. For each Dialog, provide translated response text inline or via translation file. Test language detection by greeting the bot in different languages.

  4. Enable Conversation Repair

    Bot Settings, Conversation Repair. Toggle on. The feature scans live conversations daily and produces a suggestion queue. Review the queue weekly and accept suggestions that genuinely improve the bot.

  5. Wire Einstein GPT (optional)

    Bot Settings, Generative Responses. Enable per-Dialog or per-bot. Configure grounding sources (Knowledge articles, CRM records). Test GPT responses on internal-only Dialogs before exposing customer-facing GPT.

Key options
Topic structureremember

Logical groups of related Dialogs (Order Management, Account Servicing). Customers can pick a Topic at conversation start; admins manage Dialogs per Topic.

Supported languagesremember

Multi-language within one bot. Add languages in settings; provide translated Dialog text. NLP detects customer language automatically.

Conversation Repairremember

Daily auto-detection of mishandled utterances. Suggestions land in a queue for admin review and one-click accept.

Generative Responsesremember

Optional Einstein GPT integration for dynamic responses grounded on org data. Configure carefully on sensitive use cases.

Gotchas
  • Enhanced Bot and Classic Bot are separate products. Migration is manual; there is no one-click conversion.
  • Multi-language requires translation effort per Dialog. NLP detects language automatically but does not translate Dialog response text for you.
  • Conversation Repair suggestions need human review. Accepting all suggestions blindly can degrade the bot by overfitting on edge cases.
  • Generative Responses can hallucinate on sensitive use cases. Limit to low-stakes conversations and ground on curated Knowledge articles.
  • New channel features ship to Enhanced first. Orgs on Classic miss out on Apple Business Chat rich messages, WhatsApp List Messages, and other recent additions.
§

Trust & references

Sources

Cross-checked against the following references.

Official documentation

Straight from the source - Salesforce's reference material on Enhanced Bot.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.

About the Author

Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.

§

Test your knowledge

Q1. What is an Enhanced Bot?

Q2. Should new bot projects use Enhanced or standard?

Q3. What capabilities do Enhanced Bots add?

§

Discussion

Loading…

Loading discussion…