Trace a launch from training to customer usage

Who learned it, who talked about it, and which accounts now use it, every week.

For
Revenue EnablementL&D
Routine
Every week
Needs
Juno + 2 tools
You approve
every draft

What you get

Claude
Training to customer usageShare

Since the Usage alerts training, are customers turning it on?

Used Juno, Gong and Salesforce

Launch: Usage alerts, shipped Sep 2 · Last 30 days

The funnelLast 30 days
Opened the training11 people, was 9 last week
Raised Usage alerts with a customer8 people
Accounts where Usage alerts came up23 accounts
Accounts that enabled Usage alerts14 accounts, was 12 last week
Accounts using Usage alerts9 accounts

Built by your assistant from Juno, your call recordings, and your CRM.

Reply…
Claude is AI and can make mistakes.Opus 5.5 MediumAuto

The prompt

Paste it into Claude or ChatGPT. It asks its questions in one message, then starts from what you already have in Juno.

Works in Claude, ChatGPT, and GitHub Copilot
I want to see whether our last launch changed the work, not just who completed the training: a funnel from the people who learned it, to the conversations where they used it, to the accounts or teams now using what we launched.

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. My role and the team I support
2. The launch: what shipped, its date, and the Juno training that went with it
3. Who should have learned it (teams, roles) and who they talk to about it (customers, prospects or internal teams)
4. What counts at each stage: talking about it (a mention, a demo, a next step) and using it (how much real usage, over how many days)
5. The date range
Ask these in one message, then wait for my answers.

In that same first message, also ask me which call recording or meeting notes tool, which product usage or analytics tool 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.

Pull learning activity from Juno first: who opened or completed the launch training, and how much time they spent. If you can't read completions here (analytics may be off for our account), I'll upload an export from Juno.

Then read the calls in the range, person by person: judge from the transcript whether the launch came up, who raised it, and how far it went (a mention, explained or demoed, a next step agreed, already using it). Quote at most one short line per call with its timestamp link. Never infer what was said on a call you can't read. Match accounts through the CRM, and count usage from real usage only: leave out our own staff and demo accounts.

Build the view: a funnel with one stage per step, counting people for the learning stages and accounts for the usage stages, with a conversion rate only where the unit stays the same; what changed since the last run; one dot per person (time spent learning against the share of their calls where they raised it); a timeline of every call, coloured by depth; and the gaps, each with one suggested next step. Show sample sizes, label correlation as correlation, and say which numbers you could not read.

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.

This is a read-only report: don't message, assign or notify anyone. Offer drafts (a coaching note for a person, a short refresher lesson) for me to review.

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.

What your assistant will ask you

  1. Q1My role and the team I support
  2. Q2The launch: what shipped, its date, and the Juno training that went with it
  3. Q3Who should have learned it (teams, roles) and who they talk to about it (customers, prospects or internal teams)
  4. Q4What counts at each stage: talking about it (a mention, a demo, a next step) and using it (how much real usage, over how many days)
  5. Q5The date range

How it runs

  1. 01

    Connect

    Juno and the tools below

  2. 02

    Answer

    its questions in one message

  3. 03

    Check

    the draft or the report it builds

  4. 04

    Approve it

    Nothing is published, assigned, or sent before that.

Routine: Every week. 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

  • JunoRequired
  • GongConnected in your assistant
  • SalesforceBuilt into Juno

Your assistant reads these tools and does the work in Juno.

Teams that use it