juno journey
Book a demo

Sales, CS, and Support, up to date.

Juno briefs each team in its own format and shows who's behind.

Book a demo

G24.7 / 5

Part of Revenue Enablement

The change reached Slack. It never reached the customer call.

Sales still quotes the old price, CS still demos the old flow, and Support still sends last quarter's fix.

Ramping a new rep is a different journey: Role-Based Ramp-Up.

One change, three teams briefed by Monday

Pro plan pricing changes Monday. Brief Sales, CS, and Support, and let reps practice the price objection.

Claude

What each team receives

  • Sales

    What arrives
    The new price line and the objection it will meet
    Who gets it
    AEs and SDRs, by role
    Format
    A short piece and a practice round
    What they demonstrate
    Pitch the feature
    What it replaces
    Last quarter's pricing slide

  • CS

    What arrives
    What to tell each account, and when
    Who gets it
    CSMs, by department and group
    Format
    A heads-up, then a short piece
    What they demonstrate
    Handle the objection
    What it replaces
    The old renewal talk track

  • Support

    What arrives
    The updated answer and the steps behind it
    Who gets it
    Agents, by group and location
    Format
    A heads-up
    What they demonstrate
    Walk through the troubleshooting
    What it replaces
    The saved reply that no longer applies

Keep one answer up to date

  • Update content in place

    The battlecard is edited where it already lives, so no duplicate copy is uploaded.

  • Link instead of copying

    Every place that links to it opens the current version.

  • Edits stay in draft until you publish

    Your teams don't see edits until you publish them.

See which team is still giving the old answer

  • Track each team

    See how many people in Sales, CS, and Support are up to date on the change.

  • Drill down to each rep

    Open a team to see whether each rep learned the change, raised it on calls, and used it.

  • A next step for every rep

    Every rep gets a suggested next step, from a course to a practice round.

When the gap is a skill, not a change: Close Skill Gaps as They Appear

Practice the pitch before the customer hears it

  • A branching scenario

    Each change gets its own scenario: the customer asks a question, and the rep chooses a reply.

  • Pitch certification

    The pitch is scored against your rubric, with a passing score to reach.

  • Grade open answers

    The agent grades open answers, or suggests a grade for your reviewer to confirm.

  • Recorded pitches

    Reps record the pitch on video for a validator to score.

  • A live session

    Reserved for changes big enough to need one.

You own the talk track: nothing reaches your teams until you approve it.

Try it

  • Create a sales enablement channel

    Pitch, product, and competitive material in one place reps open.

    The prompt

    Your AI asks you

    Whether you have playbooks or recorded calls, which roles, the skills and deals to win

    I want a sales enablement channel in Juno Journey where reps find pitch, product and competitive material in one place. 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. Whether we have playbooks or recorded calls, and which tools hold them 2. Which sales roles and segments this is for 3. The skills or deal types we most need to win Ask these in one message, then wait for my answers. Check each tool I name is connected in this chat; if not, I’ll connect it or upload exports. Never guess what’s in a playbook or a call. Look in Juno first for existing sales courses, quizzes and channels, and reuse them. Then propose topics (e.g. by deal stage), file existing content in, and suggest 3 new pieces for the biggest gaps (one from a strong call, if we record calls). Build it as a new private channel with drafts and preview it. Adding content to a channel with members notifies them, so ask before touching an existing one. Don’t publish, assign or notify reps until I approve.

  • Practice talking about a new feature: branching scenario

    A customer asks, your rep picks a reply, and the conversation branches.

    The prompt

    Your AI asks you

    The feature, who talks about it, real customer questions, any call notes you have

    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. 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.

  • Find who learned it but isn't talking about it

    Who finished the course but hasn't raised it with customers, and a next step.

    The prompt

    Your AI asks you

    The feature and team, whether and where you record calls, what counts as "talking about it"

    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. 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.

  • Certify the team on a new pitch

    Study it, practice it, deliver it, scored against your rubric, with a pass mark.

    The prompt

    Your AI asks you

    The pitch, your scoring rubric (or a draft), who reviews, the pass mark and deadline

    I want to certify our team on a new pitch: they study it, practice it, deliver it, and get scored against a clear rubric. 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 pitch (upload the deck or script, or tell me where it lives) 2. Our scoring rubric, or should you draft one 3. Who reviews and scores, and the pass mark 4. Who must be certified, and by when Ask these in one message, then wait for my answers. If the pitch lives outside Juno, check that source is connected in this chat; if not, I’ll upload it. Stick to our messaging; don’t invent claims. Search Juno first for existing training on this product or pitch. Then propose a certification journey: a short course on the pitch, a practice scenario, a knowledge quiz, and a final pitch reviewed against the rubric. Show me the outline and rubric first, then build the course and quiz as drafts; an interactive practice lesson goes live when saved, so preview it and save only when I say so. Don’t publish, assign or notify anyone until I approve.

All promptsNew to Juno? See it in a demo

“The journeys with automations really helped me make sure my support agents were being kept up to date on our product on a daily basis.”
Salome M.Customer Experience Training & AI Enablement Manager, Moon ActiveG2
“Speaking from my experience, Juno is the perfect combination of functionality and flexibility.”
Meagan D.Director of Sales Enablement, Hunters

The same change, for your customers and partners

Only the final delivery changes.

  • CustomersAn academy update, delivered in-app and curated. Measured by adoption, ticket deflection, and renewal.
  • PartnersA partner academy and a certification refresh. Measured by certified partner capacity and partner-sourced pipeline.
  • EmployeesSales, CS, and Support, each briefed in their own terms. Measured by who is up to date, per team and per rep.

Frequently asked questions

What is the difference between a sales enablement platform and an LMS?

A sales enablement platform manages the content reps share with buyers. An LMS delivers training. Juno is an LLM-native People Readiness Platform with an LMS as its delivery layer: each change becomes a brief for each team, a practice round, and a check on what changed in the work. Juno does not provide sales rooms, buyer analytics, or call recording.

How do you keep sales, CS and support on the same answer?

Write one change three ways, one for each team, and update the source in place, so every link opens the current version.

How do we stop reps from quoting outdated pricing?

Juno updates the pricing course and battlecard in place, briefs the reps who quote prices, and shows who still gives the old answer.

What is support enablement?

Support enablement keeps agents giving the right answer as the product, pricing, and policies change. In Juno, each change reaches Support as the updated answer and the steps behind it, sized to the change, with a check that agents can walk through the troubleshooting. Support gets its own brief, never a copy of the sales brief.

How do you measure whether enablement changed what reps do?

First by team, then by person. Call and usage data come from your own tools through your LLM, and the results show correlation, never causation.

Do we need a separate tool for sales enablement and for our LMS?

No. Juno's LMS delivers the brief, the practice round, the certification, and the reporting, beside the training your company already runs.

Can ChatGPT or Claude brief our teams when something changes?

Yes. ChatGPT, Claude, GitHub Copilot, and Cursor connect to Juno through the Juno MCP, over OAuth, with no API keys. Your LLM reads the change where it lives, in a memo, a call, or a thread, and directs Juno to update the answer, draft the practice round, and prepare the assignments. Nothing is published or assigned, and no one is notified, until you approve.