
Find who learned it but isn't using it
Completions matched with calls, a next step for each rep.
- For
- Revenue Enablement
- Routine
- Every week
- Setup
- Juno + 2 tools
- You approve
- every draft
What you get
Security 2026
by Northstar
Course
Updated September 1, 2026
The prompt
Written to ask before it assumes, check what already exists, and stop before anything goes live.
I want to find the people who completed training on a feature but aren’t bringing it up with customers, so I can help them. 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 and the date range 2. The team 3. Whether we record or summarize customer calls, and where 4. What counts as “talking about it” (a mention, a demo, a follow-up) 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 call recording or meeting notes tool and 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 that call source is connected in this chat; if not, I’ll connect it or upload transcripts. Never infer what was said on a call you can’t read. Pull completions from Juno first, confirm the matching with me, then check calls per person. If you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno. Show me a table: person, learned, calls in range, calls that mention it, an example line, suggested next step. Show sample sizes and flag anyone with too few calls to judge. Don’t message, assign or notify anyone; offer drafts for me to review. 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 week. 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 and the date range
- Q2The team
- Q3Whether we record or summarize customer calls, and where
- Q4What counts as “talking about it” (a mention, a demo, a follow-up)
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 week. 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
- JunoRequired
- Gongvia your AI assistant
- SalesforceNative
Your AI assistant reads the tools it can reach and drives Juno.
Where this Journey Play works
Journey Plays that go with it
Signature play
A learning to impact funnel for a launch
From who learned it, to who talked about it, to the accounts now using it. Every week.
Live viewEvery week
Ship on Monday, train on Tuesday
A release note becomes a click-through lesson for the teams it changes.
Every release
This month's “What's new” digest and video
Everything you shipped in one short course, plus a video on the biggest change.
Every month






















