Last session we covered customization options for the auto-run parts of Compass and got a first look at Explorer. This time, we’re going deeper on Explorer, custom Presentations, and Personas. Busy session, let’s get into it.
1. Explorer Findings
Start by heading to Explorer from the left menu bar, then click Previous Sessions near the top of the window. You should see a Session about Behavioral Health from last time. Click into it to pick up where we left off.
Check the right side of the screen for Findings. If none are showing, ask the agent in the chat window to promote its Findings. Then click on one to view it.
We’ve mentioned Findings in passing across the last two sessions — now let’s actually dig in. An individual Finding has several buttons: Chart and Table toggle those views on or off; SQL exposes the underlying query; Export downloads the table as a .csv; and Edit lets you adjust the chart format.
Click Edit to explore the options. You can update the Finding’s title, description, and chart type — and when you change the chart type, the available fields update accordingly. You can also add a secondary measure on a right y-axis if needed. The column formatting section lets you set labels, units (percent, number, dollar), and decimal precision.
The last section in Edit is labeled Presentations — this is where you can add the finding to one or more presentations. That said, you don’t have to go through Edit to do this. Click Cancel (or Save if you made changes) to return to the Finding view, then try the Add button on the far right. It opens a scrollable list where you can pick a presentation to attach it to.
2. Ad Hoc Presentations
You can also create a new presentation for this analysis by clicking + New Presentation at the bottom of the Add menu and typing the Presentation name. (You can also create a Presentation from the Presentation menu. This method gives you several more fields that you can edit or fill in, but you can also do this later from the Edit Presentation button.)
Try it out: Hit Add, select +New Presentation, type a name, and hit the Enter key. This process will automatically add the Finding to the Presentation you just created. Add a few more Findings to this new Presentation so you have something to work with, then head to Presentations in the left menu, find your new one, and click in.
You’ll land on a blank screen that cheerfully reads “This presentation has no slides yet but has [#] unused finding(s). Start building.” Since this is a custom Presentation, you’ll need to give the agent some direction. Click Build and a chat window appears. Your prompt can be as simple as “Organize my slides” or as detailed as asking for a logical flow with intro and summary slides. Type something and click Start Building. You’ll land on the same editing screen you saw when working with Opportunity Scan presentations — same process from here.
3. Diagnostic Definitions
Next up: the Diagnostics section of Compass. We’ve touched on Diagnostic Suites, but there are a few screens in here we haven’t explored yet.
Click Diagnostics in the left menu bar. The first screen is Definitions — a list of all pre-built Diagnostics in Compass, organized by Domain. These include Diagnostics built by the Ursa team as well as any you’ve created yourself (more on that shortly). You can filter these Diagnostics by their Domain or the Diagnostic Suite that they are part of. You can also look for particular Diagnostic by using the Search bar.
Click into any Diagnostic to see its Sessions and pre-built Prompts. Try clicking Population Overview: the System Prompt at the top applies to all Sessions in the Diagnostic; below that you’ll see the available Tools; and below that, the list of Sessions with their descriptions, Prompts, and any dependencies (the blue items).
From this screen you have a couple of options. The Create Diagnostic button runs this Diagnostic as a one-off — outside of any Opportunity Scan. This is useful when you want to manually step through each Session, tweaking prompts or experimenting with new Sessions as you go. The tradeoff is that you have to “babysit” the Diagnostic — starting each Session individually rather than letting it run automatically the way Opportunity Scan does.
Go ahead and click Create Diagnostic. The screen that appears looks similar to a completed Diagnostic, except each session says “Not started” instead of showing a finding count. Click Edit Diagnostic to select an Entity for this run. You can also share the Diagnostic Instance with other users (with edit access or view-only), update the System Prompt, or adjust the available tools. Click Save Diagnostic when done (or Cancel), and you’re back on the main Diagnostic screen.
Click the first Session and you’ll land on its prompt screen. Make any edits you want, then click Start Session to let the agent run. When it finishes, click the Diagnostic name at the top right to return to the main screen, then move on to the next Session. Rinse and repeat for each one.
Back on the main Diagnostic screen, the pencil icon next to any Session lets you update its name or description, or delete it if it’s no longer needed.
To add a brand-new Session, click the New Session button at the top right and write a prompt from scratch. Once created, it shows up on the main screen where you can edit its name and description, and drag it into the right order using the grid handle on the left side.
If you’re happy with the changes you’ve made and want to save this Diagnostic as a reusable Definition — available for one-off use or in an Opportunity Scan — click Edit Diagnostic again, then hit Save as Definition at the very bottom. You’ll be asked for a name (note: existing Definition names can’t be reused). From there you’ll land on the Definition screen where the default Form view shows each session in its own block. For a cleaner view of full prompts or quick edits, click the Markdown button in the top right. Save or Cancel, then click Back to Definitions to return to the list.
4. Personas
Okay — that was genuinely a lot. But there’s one more thing before we leave this screen. Notice the star next to each Diagnostic Definition? Some are yellow, and some aren’t.
Yellow means the Diagnostic Definition is available as a Persona in Explorer. The default Persona is called Analyst Assistant — the one powering the Explorer session you ran above. Scroll down to the Explorer domain on the Definitions screen and click into Analyst Assistant to read through the prompt. It’s quite prescriptive: it tells the agent exactly how to handle general analytics questions, how to work with the data model, and how to interact with the user. You’ll also notice it’s labeled as the Default Persona in the top right.
There can conceivably be use cases for other Personas (one focused on data integrity, one to help you find specific objects / fields in the Ursa data model, etc.), but this is likely something that you would work with your Ursa team to develop.
To see the Personas in action, click Explorer in the left menu. You’ll see a Persona dropdown above the prompt window, defaulted to Analyst Assistant. Open it, and any other Personas available for your organization will appear for you to select.
Selecting a Persona gives the agent access to the system prompt from that Diagnostic Definition, not its sessions or the results of any particular run. (To tap into the context from a specific Diagnostic Instance (like the findings from a prior run), you’d use the follow-up chat window within that instance, the way we did for next-level analysis from a Presentation.)
5. Diagnostic Instances
Okay, that was a worthwhile detour — but now back to Diagnostics. Click it in the left menu bar. We’ve covered Definitions pretty thoroughly; let’s move to the next screen: Instances.
By default, this screen shows only Diagnostics you’ve run one-off (labeled as Other) — so it may be empty for you right now. The filter at the top lets you pull in Diagnostic Instances from Scans or from Explorer. Try checking them to see how the list fills out.
You can also search this screen for a particular Diagnostic, filter to Diagnostics run on a particular Entity, or filter to the Owner (usually the Creator) of the Diagnostic. By default, the list is sorted by the Diagnostic with the most recent activity (Last Activity column).
You’ll use this screen mainly for reviewing / editing prior ad hoc Diagnostics or kicking off a new one from scratch.
When you’re starting out, the easiest path to generate a new Diagnostic is to create a Diagnostic Instance from an existing Definition and edit it to fit your new questions — we covered that earlier in this session. At some point you’ll want to build something different enough that it makes sense to start from scratch. That process is a bit more technical, so we’ve dedicated a full separate session to it (Session Four). Take your time getting comfortable first, and tackle it when you’re ready.