Compare trained and untrained accounts
Usage side by side, clearly labeled as correlation.
- For
- Customer Education
- Routine
- Every quarter
- Needs
- Juno + 1 tool
- You approve
- every draft
What you get
CalendarTarnwell Academy
Learn from your company and colleagues' knowledge.
Search Tarnwell AcademySearch
Channels
Getting started with Tarnwell
Updated Sep 28

Setting up your workspace
Updated Sep 20

Running your first report
Updated Sep 12
Tarnwell certification
Updated Aug 30
The prompt
Paste it into Claude or ChatGPT. It asks its questions in one message, then starts from what you already have in Juno.
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.
What your assistant will ask 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
How it runs
- 01
Connect
Juno and the tools below
- 02
Answer
its questions in one message
- 03
Check
the draft or the report it builds
- 04
Approve it
Nothing is published, assigned, or sent before that.
Routine: Every quarter. The prompt offers to set it up as a scheduled task in your assistant, only after you approve.
Live viewLive view: if your assistant supports artifacts connected to Juno, you get an interactive view that reads Juno again each time you open it.
What it connects
- SalesforceBuilt into Juno
- JunoRequired
Your assistant reads these tools and does the work in Juno.
Teams that use it
Journey Plays that go with it
Design the customer academy homepage
A branded public homepage with your real courses, for you to preview first.
BetaOnceFind stale, missing, or duplicate courses
A short list of what to update, merge, or retire.
Live viewEvery quarterBring your Storyline and Rise courses into Juno
Imported once, edited in plain words; links, assignments, and versions stay.
Once



























