
Practice a new feature conversation
A branching scenario: the customer asks, the rep picks, it branches.
- For
- Revenue Enablement
- Routine
- Every launch
- Setup
- Juno + 1 tool
- You approve
- every draft
What you get
Example data
Channel · for salesSales Win Room3 new this week
Objection Handling
by Northstar
Updated September 28, 2026
Competitive Positioning
by Northstar
Updated September 24, 2026

Pricing and packaging
by Northstar
Updated September 9, 2026
The prompt
Written to ask before it assumes, check what already exists, and stop before anything goes live.
I want a branching practice scenario in Juno Journey where people rehearse talking about a new feature with a customer and see where each answer leads. 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 problem it solves 2. Who talks about it (sales, CS, support) 3. The questions and objections customers really raise 4. Call notes or transcripts we can use as examples, if any 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 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. For sources outside Juno, check they’re connected in this chat; if not, I’ll paste excerpts. Never present invented quotes as real. Search Juno first for training on this feature so the scenario matches it. Then outline a customer persona, 3-4 decision points, strong and weak answers with feedback, and a score. After I approve, build it as an interactive HTML lesson with SCORM tracking and preview it. Saving it to Juno puts it live in our catalog, so save only when I say so; don’t assign it. Routine: after the first run, offer to repeat this for every launch. 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 problem it solves
- Q2Who talks about it (sales, CS, support)
- Q3The questions and objections customers really raise
- Q4Call notes or transcripts we can use as examples, if any
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 launch. The prompt offers to set it up as a scheduled task in your assistant, only after you approve.
What it connects
- JunoRequired
- Gongvia your AI assistant
Your AI assistant reads the tools it can reach and drives Juno.
Where this Journey Play works
Journey Plays that go with it

A sales enablement channel
Pitch, product and competitive material in one place reps open.
Once, then kept current
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






















