juno journey
Book a demo

Sales, CS and Support, current on every release and every change.

A price, a pitch, a policy changes on a week when nothing ships. Your LLM reads the change and Juno briefs Sales, CS and Support in three different shapes, then shows you who is still giving the old answer.

Book a demo

4.7 / 5G2

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.

How it works

1Trigger & Signal

  • Google DriveThe pricing memo, the playbook
  • GongWhat customers ask
  • Salesforce / HubSpotThe deals
  • SlackThe thread where it was decided

2Knowledge Design

Your LLM + Juno MCP

    • Mission-critical
    • Important, not urgent
    • Nice to know
    Human approval

    3Delivery & Adoption

    • SalesThe new line and a practice round
    • CSWhat to tell the account
    • SupportThe updated answer

    4Measure

    Who is still giving the old answer

    One change, three teams briefed by Monday

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

    Claude

    One change, three teams, three different sentences

    • Sales

      What arrives
      The new price line and the objection it will meet
      Who gets it
      AEs and SDRs, by role
      At what size
      A short piece and a practice round
      What they show us
      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
      At what size
      A heads-up, then a short piece
      What they show us
      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
      At what size
      A heads-up
      What they show us
      Walk through the troubleshooting
      What it replaces
      The saved reply that no longer applies

    One live answer, not five versions of it

    • Updated in place

      The battlecard is edited where it lives. No copy is uploaded beside it.

    • Linked, not copied

      Every place that links to it opens the current version.

    • Draft until you publish

      Edits stay invisible to the field until you publish them.

    See which team is still giving the old answer

    • Per team

      Sales, CS and Support each show how many are current on the change.

    • Per person

      Open a team to see each rep: learned it, said it, used it.

    • A next step each

      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

    Practise the pitch before the customer hears it

    • A branching scenario

      Each change gets its scenario: the customer asks, the rep picks a reply.

    • Pitch certification

      The pitch is scored against your rubric, with a pass mark to clear.

    • Open answers validated

      The agent grades open answers, or suggests a grade your reviewer confirms.

    • Recorded pitches

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

    • A heads-up

      Most changes need a short post, not a course.

    • A short piece

      A few minutes on what changed and what to say now.

    • A practice round

      The objection rehearsed before it comes up on a call.

    • A live session

      A room, for the change big enough to need one.

    You keep the talk track: nothing reaches the field before you approve it.

    Try it

    • Create a sales enablement channel

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

      Your AI asks you

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

      New to Juno? See it in a demo
      The prompt

      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 a question, your rep picks a reply, and the conversation branches from there.

      Your AI asks you

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

      New to Juno? See it in a demo
      The prompt

      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

      The people who finished the course but haven't raised it with customers, with a next step for each.

      Your AI asks you

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

      New to Juno? See it in a demo
      The prompt

      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.

      Your AI asks you

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

      New to Juno? See it in a demo
      The prompt

      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.

    Every prompt

    “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 at Moon ActiveSalome 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 at HuntersMeagan D.Director of Sales Enablement, Hunters

    The same week, one org further out

    The same journey runs for your customers and your partners. Only the last mile changes.

    • CustomersAn academy update, in-app and curated. Measured on adoption, ticket deflection and renewal.
    • PartnersA partner academy and a certification refresh. Measured on certified partner capacity and partner-sourced pipeline.
    • EmployeesSales, CS and Support, each in their own words. Measured on who is current, per team and per rep.

    Questions people ask.

    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 per team, a practice round and a check in the work. Sales rooms, buyer analytics and call recording are not our layer.

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

    Start from one change and write it three ways. Sales gets the new line and a practice round, CS gets what to tell the account, Support gets the updated answer. The source is updated in place, so every link opens the current version, and you see per team who is still giving the old one.

    How do we stop reps quoting outdated pricing?

    Update the answer where it lives instead of adding a new file beside it. Juno edits the pricing course and the battlecard in place, so every link opens the current version. Then it briefs the reps who quote prices, lets them practise the objection, and shows you who has not changed their answer yet.

    What is support enablement?

    Support enablement keeps agents giving the right answer as the product, the price and the policy 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 is its own lane, never a copy of the sales brief.

    How do you measure whether enablement changed what reps do?

    Per team, then per person. For each rep you see whether they learned the change, whether they raised it on calls and whether their accounts use it, with a suggested next step. Call and usage data come from your own tools through your LLM, and the read is correlation, never causation.

    Is this the same as onboarding new reps?

    No. Onboarding ramps a new rep to their first quota. This journey keeps the reps you already ramped current when a price, a pitch or a policy changes, months later. Ramping a new rep is Role-Based Ramp-Up. When the change has a date of its own, see Release & Product Update.

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

    No. Juno is one People Readiness Platform, and its LMS is the delivery layer for every team: the brief, the practice round, the certification and the reporting sit in one place, beside the training your company already runs. What each plan includes is on the Pricing page.

    Can ChatGPT or Claude brief our teams when something changes?

    Yes. ChatGPT, Claude and Copilot 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 drives Juno to update the answer, draft the practice round and prepare the assignments. Nothing is published, assigned or notified before your OK.