
Compare adoption: trained vs untrained accounts
Usage side by side, labelled as correlation.
- For
- Customer Education
- Routine
- Every quarter
- Setup
- Juno + 1 tool
- You approve
- every draft
What you get
Example data
CalendarNorthstar Customer Academy
Learn from your company and colleagues' knowledge.
Search your Northstar Customer AcademySearch
Channels
Getting started with Northstar
Updated September 28, 2026

Setting up your workspace
Updated September 20, 2026

Running your first report
Updated September 12, 2026
Northstar certification
Updated August 30, 2026
The prompt
Written to ask before it assumes, check what already exists, and stop before anything goes live.
I want to compare feature adoption for accounts whose owners took the training vs. those whose owners didn’t. Use the Juno Journey connector for anything in Juno. If it isn’t connected, stop and tell me how to add it (https://docs.junojourney.com/mcp/overview). Before you build anything, ask me: 1. The feature, the training that covers it, the date range 2. Whether and where we track product usage, and which event means “used it” 3. Where account owners are recorded (if anywhere) and how they match Juno users 4. Accounts or segments to exclude Ask these in one message, then wait for my answers. In that same first message, also ask me my role and the team I support, and which CRM we use. Then check each one is connected in this chat; if not, I'll connect it or upload an export. Never guess what is in it. Check each non-Juno source is connected in this chat; if not, I’ll connect it or upload a CSV. Never estimate missing numbers. Pull completions from Juno first and show how you matched people. If you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno. Then build an interactive artifact: adoption for trained vs. untrained owners, counts per group and the account list. State definitions, show sample sizes and gaps, and say plainly it’s correlation, not causation. Change nothing anywhere. If this assistant supports artifacts connected to Juno, build it as an interactive artifact that re-reads Juno each time I open it, and say so; otherwise build it static and show the date the data was read. Routine: after the first run, offer to repeat this every quarter. If this assistant can run scheduled tasks, set one up only after I approve it; if not, give me a one-line prompt I can re-run.
Your AI asks you
- Q1The feature, the training that covers it, the date range
- Q2Whether and where we track product usage, and which event means “used it”
- Q3Where account owners are recorded (if anywhere) and how they match Juno users
- Q4Accounts or segments to exclude
The routine
- 01
Connect
Juno and the tools below
- 02
Answer
the questions, one message
- 03
Review
the draft or the view it builds
- 04
You approve
before anything goes live
Routine: Every quarter. The prompt offers to set it up as a scheduled task in your assistant, only after you approve.
Live viewLive view: when your assistant supports artifacts connected to Juno, the result is an interactive view that reads Juno again each time you open it.
What it connects
- SalesforceNative
- JunoRequired
Your AI assistant reads the tools it can reach and drives Juno.
Where this Journey Play works
Journey Plays that go with it

Design the customer academy homepage
A branded public homepage with your real courses, previewed first.
BETAOnce
Audit the academy: stale, missing, duplicated
A short list of what to update, merge or retire.
Live viewEvery quarter
Bring your Storyline and Rise courses into Juno
Imported once, then edited in plain words: same link, same assignments, every version kept.
Once






















