A financial services company uses Salesforce Service Cloud with Einstein Bots to handle account balance inquiries. The bot currently uses a standard intent 'CheckBalance' which recognizes phrases like 'What is my balance?' and 'Show my account balance.' The company wants to expand the bot to also answer questions about recent transactions, such as 'What were my last five deposits?' and 'Show my recent withdrawals.' The system administrator has added a new intent called 'RecentTransactions' and mapped it to a new flow. However, during testing, the bot often misclassifies 'CheckBalance' requests as 'RecentTransactions' when the user mentions a specific amount or date. Which action should the administrator take to resolve this misclassification?
Providing more training data for the existing intent helps the model distinguish between similar phrases.
Why this answer
Adding sample utterances that include amounts and date ranges to the 'CheckBalance' intent provides the Einstein Bot's natural language processing (NLP) model with more training data to distinguish between balance inquiries and transaction requests. This improves intent classification accuracy by reducing overlap in the phrases the bot recognizes, directly addressing the misclassification issue.
Exam trap
The trap here is that candidates may think lowering the confidence threshold or creating separate bots will fix misclassification, but the correct approach is to enrich the training data for the existing intents to improve the NLP model's accuracy.
How to eliminate wrong answers
Option B is wrong because reducing the confidence threshold would cause the bot to match intents more loosely, likely increasing misclassifications rather than resolving them. Option C is wrong because disabling the 'RecentTransactions' intent would prevent the bot from handling transaction inquiries at all, which contradicts the expansion goal. Option D is wrong because creating a separate bot for transactions adds unnecessary complexity and does not fix the root cause of intent confusion; the same misclassification could occur if users are routed incorrectly.