My favorite part of this RovoCon was meeting people (I'm betting this will be my favorite part of Vancouver's as well!). So, putting that aside, my next favorite bits were:

1. Rovo prefers markdown in prompts - Using markdown in prompts helps in a few ways. First it visually breaks up the prompt. making it easier for humans to read it. (It's MUCH easier to find "## Formatting" than to dig through text for formatting instructions!). It also makes it much easier to reference specific sections of a prompt since Rovo can easily find it.
2. Role vs Scenario - Role defines what the agent should be doing, the scenario provides more specifics about how and when it will be doing that. For example, an agent may be specifically setup to help improve a knowledge base article, but it may do this different ways depending on the type of information on the page.
3. Human-in-the-loop - Rovo will keep a human in the loop especially when it uses a skill. This is important for a few reasons... mainly, it helps ensure that a human will confirm the action is appropriate. (and it's good reassurance that Rovo won't go rogue...).
   

Back to my favorite part - the people!
A large part of my job is to talk into a camera, which means many of you know what I look and sound like, but I have no idea what you look or sound like. Getting to go to in-person events means I get to meet people for real. (I met several folks who had been in live streams with me, and we could pinpoint the specific one since they provided specific comments!).

The personal connection was also great, but I had a number of good discussions with folks on using Rovo. Topics included:

1. Working with compliance teams - A big topic around Rovo is how to use it safely. Compliance/legal teams are VERY interested in this, so finding ways to get them the information they need is important. Honestly there are some feature gaps in Rovo here - for example I can't prevent a specific user from using Rovo currently - however, our relationship with compliance teams is critical to building trust.

2. Adoption -  How to get a company of more than 1 person to understand how to use Rovo came up quite a bit. Some strategies included training champions (who would bring back skills to their teams), to showcasing good use cases (highlighting specific use cases), to hosting in-person "hack a thons" to come up with ideas.

I've got a LOT of video content to work through! Be on the lookout for more videos (including some interviews, recorded sessions and more!). I'm really looking forward to Vancouver (for may reasons) - and let me know what else you want to learn!