Einstein Copilot Basics | Salesforce Trailhead

#salesforce
#trailhead
#salestraining
#salesforcetrailhead

Believe it or not, by the end of this unit Linda will have successfully launched an AI assistant in Cloud Kicks’s Salesforce org, achieving the first of many AI-driven productivity boosts for her users. But how does she do it?

This final stretch of Linda’s journey begins with a test drive of Cloud Kick’s copilot, and it ends with happier, more efficient users. So let’s hit the road!

The Importance of Testing
If you’re a Salesforce admin or developer, you understand how important it is to test new technology and software before releasing it to users.

Don’t launch your new copilot without testing it first to ensure good performance. Does the copilot accurately interpret a user’s request or instruction? Does it launch the right actions? Does it provide helpful, accurate responses?

Of course, all the tools you need for testing your copilot are baked right into the Copilot Builder. Here are a couple of tips to get you started with the testing process.

Think like a user: Test the copilot with requests your users might make. What types of users will have access to the copilot? What questions are they likely to ask during a copilot conversation? What terminology and wording would they use? Consider creating a spreadsheet to track sample user inputs (called utterances) to make sure you’re covering a wide variety of test cases and scenarios. We recommend testing with at least 30 utterances to ensure good performance.
Use dummy data: You don’t want to accidentally update real customer data during the testing process. Make sure you have a set of dummy records in your org that you can use when you’re testing a copilot.

Introduction
Get Started with Einstein Copilot
Explore Einstein Copilot
Enable and Customize a Copilot
Test and Activate a Copilot