Test and Activate a Copilot

Learning Objectives

After completing this unit, you’ll be able to:

• List the best practices for testing a copilot.
  
• Test a copilot to see how it performs.
  
• Grant users permission to access Einstein Copilot.
  
• Activate a copilot.
  
• Explain how to monitor a copilot and evaluate the performance.
  

The Final Stretch

Believe it or not, by the end of this unit Linda will have successfully launched an AI agent 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 Agent 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 to make sure you’re covering a wide variety of test cases and scenarios. We recommend testing with at least 30 user inputs 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.
  
• Test on Salesforce Mobile: Think of how your users might interact with Einstein Copilot on Salesforce Mobile, and test out some scenarios after activating your copilot. Try out voice input and be wowed by its magic.
  

Simulate a Conversation with the Copilot

Linda’s ready to roll up her sleeves and get ready to test! As you learned during the tour of the Agent Builder UI, Linda will use the Conversation Preview panel to simulate how a user might interact with the copilot.

Linda comes up with a request that one of her sales reps might make during a copilot conversation. She types, “Summarize the Acme deal” in the chat window and presses Enter.

As Linda interacts with the copilot in the chat window, the Plan Canvas dynamically updates, and Linda watches as the reasoning engine builds a plan and launches actions to carry out the request.

After the copilot is done working on her request, it provides the exact response Linda was looking for: a summary of the Acme opportunity. Linda reviews the list of actions the reasoning engine triggered to get that response. Everything looks good, so her first test was a success! She continues this process until she’s covered all the necessary test cases to ensure a good experience for her copilot users.

Monitor and Troubleshoot User Interactions

As you can imagine, Linda is thrilled about the positive outcome of her first test conversation with Cloud Kicks’s copilot. But what if her test had failed? Maybe the copilot triggered the wrong action, returned an error, or generated an inaccurate response. How would Linda troubleshoot those issues?

One tool Linda can use is the event logs. We introduced event logs in the previous unit. Let’s take a closer look now.

To view the event logs:

1. Make sure the copilot is open in the builder.
   
2. Select the Event Logs tab.
   

Linda can see all the interactions that have happened so far with the copilot. She can go to a particular session to debug the copilot’s performance and get to the bottom of any issues, such as errors, incorrectly triggered actions, or incomplete plans.

The event logs are an invaluable troubleshooting tool during the testing phase and beyond. After the launch, Linda can use the logs to monitor and troubleshoot the copilot’s interactions with her Salesforce users.

Enable User Permissions

Let’s fast forward to the point where Linda has successfully completed all her testing, and she’s ready to launch the copilot in her Salesforce org. To make the copilot available to users, Linda has to grant users permission to access the feature and activate the copilot. Let’s enable the permission set group first.

Remember, Linda and the Cloud Kicks leadership team decided to start small and roll out Einstein Copilot to a limited number of users to get feedback before making the copilot widely available. She thinks Cloud Kicks’s sales reps will get a huge productivity boost by using an AI agent in Salesforce, so she enables the feature for key members of the sales team first.

To assign user permissions:

1. From Setup, enter Users in the Quick Find box, then select Users.
   
2. In the list view, click the user’s name to view the user details page.
   
3. Scroll down to the Permission Set Group Assignments section, then click Edit Assignment.
   
4. Select the Einstein Copilot for Salesforce User permission set group, then click Add.
   
5. Click Save.
   
6. Repeat the process for other users who need access to Einstein Copilot.
   

Get Ready for Launch

Linda is getting close to launching Copilot in her org! Before she flips the switch and activates her copilot, she makes sure her users are prepared to use an AI agent in Salesforce.

Thankfully, Linda has been following the company’s standard change management process to ensure a successful rollout of Einstein Copilot, which includes things like creating a communication plan and training end users so they get the most out of the feature. We recommend you do the same.

To learn more, check out the Change Management for AI Implementation module.

Activate the Copilot

Linda’s big moment has finally arrived! With the necessary user permissions in place, the only remaining step is activating the copilot. ​​Activating the copilot makes it immediately available to users and allows them to interact with it. Here’s what she does.

1. From Setup, enter Agents in the Quick Find box, and then select Agents.
   
2. Click the name of your copilot.
   
3. Click Open in Builder.
   
4. Click Activate.
   

Cue the fanfare and the confetti! The new AI agent is now available to Cloud Kicks’s sales reps to help them with common business tasks in Salesforce, both on desktop and mobile devices. Cloud Kicks’s AI transformation is well underway.

Happy Users, Happy Admin

A couple weeks after the launch, Linda gathers feedback from the sales reps using Einstein Copilot. Linda sends out a quick survey to get more details about the benefits of having an AI agent in Salesforce.

On average, the sales reps estimate that they’re saving about 1 hour a week by using Einstein Copilot, which means Cloud Kicks’s new AI agent is making users more productive. The sales reps are thrilled because time is money. And that means Linda is thrilled, too. Happy users make a happy admin!

Best of all, Linda knows her users’ productivity gains will only increase as Cloud Kicks rolls out the copilot to more users and starts to implement use cases for custom topics and actions. And it goes without saying that Einstein Copilot will only get more powerful in later Salesforce releases. The future looks bright!

Resources

• Salesforce Help: Troubleshooting Agents and Copilot