Automations for Enablement
Last updated: July 29, 2026
Reinforce process, scorecards, and daily rhythm across the team. These templates flag non-compliant calls and put a ready-made standup brief in Slack before the meeting starts.
Browse them under Automations → Templates → For Enablement. For prompt craft and testing: Writing effective automations.
How to start from a template
Go to Automations → Templates.
Filter For Enablement.
Click Use Template.
Name it, choose workspace or team scope, Next.
Tune Trigger / Condition / Action, Run Test, Publish.
Scorecard Compliance Check
Know quickly when a call misses required scorecard or process criteria — with what was missed and one follow-up action.
Trigger
After a real call ends
Condition (optional)
On by default. Make this concrete to your scorecard — vague Conditions create noisy alerts.
Did the rep miss important scorecard criteria or fail to follow the expected sales process during this call?
Action
Medium: Slack
Message: Send a scorecard compliance alert. Highlight the missed criteria, cite the relevant call behavior, and recommend one follow-up action.
Audience: yourself
Tips: Keep the Condition on. Split into separate automations per scorecard theme if one Condition is doing too much. Route to enablement channels or manager DMs depending on who owns the follow-up. Run Test on a known non-compliant past call before publishing.
Team Standup Summary
Walk into standup with a Slack brief already written from recent call activity and upcoming meetings.
Trigger
Daily at 8:30 — business days only (your browser timezone by default)
Move the time to right before your standup.
Action
Medium: Slack
Message: Create a concise team standup summary from recent call activity and upcoming meetings. Include priorities, risks, and follow-up reminders.
Audience: individual teams/ Channel
Tips: Scope to Selected Team so each pod gets its own note. Ask for standup-ready format (“owner + one-liner per priority; risks separate; max 8 lines”). Shared standup channels usually beat personal DMs.
Learning-module Triggers aren’t separate Enablement templates — they live under Learning Modules when you build a custom automation. Here’s the full Enablement article with those added.
Automations for Enablement
Reinforce process, scorecards, learning completion, and daily rhythm across the team. Use the For Enablement templates for call process and standups, and build Learning Modules automations when you need completion reports or overdue alerts.
Browse templates under Automations → Templates → For Enablement. For how Triggers, Conditions, and Actions work — and how to write them well — see Writing effective automations.
How to start from a template
Go to Automations → Templates.
Filter For Enablement.
Click Use Template.
In Automation Settings, name it and choose Who is this Automation for? — Everyone in the Workspace or Selected Team.
Click Next, review Trigger / Condition / Action, set Slack or email recipients, Run Test, then Publish.
Templates are starters. Change anything before you publish.
To build a Learning Modules automation from scratch, click New Automation, then set the Trigger category to Learning Modules (details below).
Scorecard Compliance Check
Know quickly when a call misses required scorecard or process criteria — with what was missed and one follow-up action.
Trigger
After a real call ends
Condition (optional)
On by default. Make this concrete to your scorecard — vague Conditions create noisy alerts.
Did the rep miss important scorecard criteria or fail to follow the expected sales process during this call?
Name the items that matter: discovery questions, next-step date, competitor handling, economic buyer, and so on.
Action
Medium: Slack
Message: Send a scorecard compliance alert. Highlight the missed criteria, cite the relevant call behavior, and recommend one follow-up action.
Audience: yourself
Tips: Keep the Condition on. Split into separate automations per scorecard theme if one Condition is doing too much. Route to enablement channels or manager DMs depending on who owns the follow-up. Run Test on a known non-compliant past call before publishing.
Team Standup Summary
Walk into standup with a Slack brief already written from recent call activity and upcoming meetings.
Trigger
Daily at 8:30 — business days only (your browser timezone by default)
Move the time to right before your standup.
Condition (optional)
Off by default. Turn one on only if you want to skip empty mornings.
Action
Medium: Slack
Message: Create a concise team standup summary from recent call activity and upcoming meetings. Include priorities, risks, and follow-up reminders.
Audience: Yourself/ Team members
Tips: Scope to Selected Team so each pod gets its own note. Ask for standup-ready format (“owner + one-liner per priority; risks separate; max 8 lines”). Shared standup channels usually beat personal DMs.
Learning Modules Completion Report
Get a scheduled rollup of who has finished (and who hasn’t) on the modules you care about — without exporting progress by hand.
Trigger
Completion Report (under Learning Modules)
Configure:
Learning Module(s) — search and add the modules to include
Frequency — Weekly, Bi-Weekly, or Monthly
Day of week / Day of the month, Time of day, and Timezone (depending on frequency)
Condition (optional)
Add one only if you want the report skipped unless something specific is true (for example, completion below a threshold). Many teams leave Condition off and let the Action summarize status every run.
Action
Medium: Email
Message: Create a completion report for the selected learning modules. List who’s complete, who’s in progress, and who’s not started. Call out anyone at risk of missing the due date, and recommend one follow-up for enablement.
Audience: Yourself/ Team
Tips: Put this in an enablement channel if the whole team should see progress; use email if leaders want a standing digest. Be explicit about format (“table-style bullets: name, status, due date”).
Good to know: This automation automatically deactivates after the learning module’s due date has passed — so it’s built for active assignments, not forever-running reports.
Reps Overdue for Learning modules
Get alerted when reps are past the due date on a learning module — so follow-ups happen before training quietly slips.
Trigger
Reps Overdue (under Learning Modules)
Configure:
Learning Module(s) — the modules to watch
Days Overdue — how many days past due before the automation fires (for example,
1for next-day nudges,3for a grace window)
Condition (optional)
Often left off if Days Overdue already defines the bar. Add a Condition if you only want alerts for certain teams, roles, or modules in a multi-module setup.
Action
Medium: Email
Message: Send an overdue learning alert. Name the rep, the module, how many days overdue, and one clear next step (nudge the rep, loop in their manager, or extend the due date).
Audience: yourself/ team