Remind the people who haven't finished
A reminder drafted for each overdue person, sent only when you say so.
- For
- HRLegal / IT
- Routine
- Every week
- Needs
- Juno + 2 tools
- You approve
- every draft
What you get
All ActivitiesCompliance 2026 by department+ Create ViewGroup by Department
Security 2026PolicySecurity 2026Course · Updated Sep 1UsersUnits
DepartmentUsersOverdue usersCompletion rate
Sales423Users 42 · Overdue users 388%
HR120Users 12 · Overdue users 0100%
Product361Users 36 · Overdue users 194%
Marketing184Users 18 · Overdue users 471%
Customer Success242Users 24 · Overdue users 283%
Finance90Users 9 · Overdue users 0100%
Average score86%
Avg time to complete18 min
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
Remind the people who have not finished: Send a personal, non-shaming reminder to the people who have not finished an assigned training, after I have seen exactly who gets it and exactly what it says. ═══ ONE ROUND OF QUESTIONS ═══ Ask me in ONE message, then wait: 1. Which training. Find it by name (search_lms_content) and confirm. 2. Who counts as behind: not started, in progress, or both; and whether to limit it to a team, department, or the people I manage. 3. The tone: gentle, firm, or final notice. 4. The deadline to mention, if any. In that same first message, also ask me my role and the team I support, and which team chat 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. ═══ THE LIST, HONESTLY SOURCED ═══ If learning data is enabled on our account, pull the learners behind on this training from it (learning_activities_query), scoped as I said, and show me the count and a named sample of up to eight. If it is not enabled, say so in one line and offer two ways in: I export the learner list from the training's analytics page in Juno and paste it, or I paste names or emails directly. Never guess, reconstruct, or invent who is behind. If the list is longer than you can show, tell me the total and where to see the rest in Juno. ═══ THE MESSAGE, THEN STOP ═══ Draft the reminder in the chosen tone: two to four sentences, assumes busy rather than negligent, one clear ask, the deadline if there is one, and a link to the training. No comparisons to colleagues, no completion percentages, no consequences I did not state, no promise of automatic follow-ups. Use only the personalisation fields the platform supports (list_notification_variables). Show me the recipients and the exact text and wait. ═══ SEND FROM THE CARD ═══ Open it for review (prepare_notification) with the recipients and text filled in; I send from there. Offer to pre-draft the next, firmer version so it is ready if we need it. If the deadline should move for everyone still open, say what that changes before you do anything. Rules throughout: the list comes from real data or from me, never from guesswork; recipients and text shown before anything opens; every send fires from a card I confirm; a private nudge, never a public callout; talk in product terms, not tool names. 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
- Q1Which training. Find it by name (search_lms_content) and confirm.
- Q2Who counts as behind: not started, in progress, or both; and whether to limit it to a team, department, or the people I manage.
- Q3The tone: gentle, firm, or final notice.
- Q4The deadline to mention, if any.
How it runs
- 01
Connect
Juno and the tools below
- 02
Answer
its questions in one message
- 03
Check
the draft or the report it builds
- 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.
What it connects
- JunoRequired
- SlackBuilt into Juno
- Microsoft TeamsBuilt into Juno
Your assistant reads these tools and does the work in Juno.
Teams that use it
Journey Plays that go with it
Roll out a policy and prove it landed
A short course, a 5-question check, and an acknowledgment, with who's done.
Every policy changeSee the compliance gaps before the deadline
Overdue training first, sorted by team and topic, ready for the audit.
Live viewEvery weekAssign harassment training by state and role
Each person gets the version for their location and role, from your HRIS.
Every year




























