This article explains how to create and schedule custom and standard notifications within Momenta—at the journey, cohort, team, or participant level. Use this to manage comms, reminders, and nudges across your program.

Overview
Audience Levels
Journey-Level Notifications
Cohort-Level Notifications
Participant-Level Notifications
Team-Based Notifications
Standard Notifications
Creating a Custom Notification
Conditions for Sending
Edit or View Sent Notifications
Testing Notifications
Watchouts
Combining with Other Systems
Dynamic Conditions Matrix
Visual Aids

Overview

Notifications in Momenta help you guide participants through their learning journey. You can use in-app messages or email, and control when, how, and to whom they are delivered.

Delivery types: Email or In-App

Notification types: Scheduled (custom), Standard, Social (not covered here)

Audience Levels

Journey: Notifies all participants across all cohorts.
Cohort: Notifies participants in a specific cohort.
Team: Targets members of a selected team within a cohort.
Participant: Sends to a specific participant only.

Journey-Level Notifications

Go to the Notifications tab inside your Journey.
Select Scheduled and click + to create a new notification.
Set audience to Journey, Cohort (multi-select), or Team.
Note: You cannot send to individual participants or use “Send Now” from this view.
Don’t forget to click Exit and Unlock when done.

Cohort-Level Notifications

Navigate to the Cohort via Experiences & Cohorts.
Select the 3 dots > Cohorts > Scheduled Notifications.
Click + to create a new notification.
Platform Notifications Toggle: Use this to enable/disable sending notifications.

Participant-Level Notifications

Go to Participant Tab in the cohort.
Select specific users > Participant Actions > Send Notification.
Important: Once you click OK, the notification is final—no edits allowed.
Use “Re-Run” to resend; no confirmation pop-up appears.

Team-Based Notifications

Set up from Journey Notifications tab or Cohort > Teams tab.
Click “Send Notification” or “Add Team Notification”.

Standard Notifications

Standard notifications are prebuilt system nudges. They are:

On/Off for the entire journey
Not editable for: title, audience, subject, timing
Editable for: message body, from/reply-to email, CC/BCC

Examples:

New Content Available
Inactive Nudge
No First Connection
Falling Behind
Workshop Starting Soon
Coaching Call Reminder
Action Due Soon

Creating a Custom Notification

Type: Email or In-App
Email: Includes title, subject, body, CC/BCC, reply-to, from
In-App: Title and message only; shown when user logs in
Use tokens to personalize messages
You can attach files/images but always test before sending

Conditions for Sending

Static Time: Set specific future date/time
Dynamic Time: Based on blueprint anchors (e.g., “3 days after Module A available”)
Send Now: Immediate delivery (only from cohort level)

Edit or View Sent Notifications

View scheduled/sent notifications from Journey or Cohort level
Click Edit to change content/timing (before scheduled send)
Download a report (Excel) for delivery/open status
View participant record for notification history

Testing Notifications

Journey Test Account: Enter email(s) to receive all triggered messages
Recommended for safe testing of layout, tokens, formatting
Use static future date for time-based testing
Note: Test account only works at Journey level

Watchouts

Participant notifications can’t be edited after creation
Standard notifications apply to all cohorts—can’t limit scope
All notifications use sender’s local time
If you CC/BCC yourself, you’ll receive one email per participant
Spacing behaves differently—return = paragraph spacing
If you disable Platform Notifications, mailers won’t send, but reports may still show as generated

Combining with Other Systems

Coordinate Momenta notifications with other platforms (Coach OS, 360, Outlook, ACT, etc.). Example:

Momenta: Journey reminders, GoDos, workshops
Coach OS: Coaching confirmations/reminders
360 Platform: Feedback and login emails
Salesforce (ACT): Action tracking reminders

Here's a table to help you understand where different mailers come from


Mailer type	Where built	To Do
Welcome to the overall journey	Momenta	Must be created
Content related reminders or comms incl. Go Dos	Momenta	Must be created
Reminders to book a session	Momenta	Must be created
Coaching session confirmations and reminders	Coach OS or Global Scheduler	Must be customised
360 access / login and welcome email	360 platform	Check if needs customisation
360 participant and rater reminders	360 platform	Check if needs customisation of text or frequency
ACT reminders	Salesforce	Check if needs customisation
Workshop invitations (where we are not scheduling using Coach or Global Scheduler)	Either Outlook or Momenta	Must be created
Strength Finder, Cvent Surveys, other 3rd party logins or links	Outlook or Momenta	Must be created

For more, see the Mailer Matrix & Communications Plan Template.

Dynamic Conditions Matrix

A full matrix of dynamic notification anchors and conditions is included here:

Condition	Qualifying element	Definition	Comments	Before / After
OptIn	To address	Based on a user completing the opt-in block in a content object, which is used as a waitlist for coaching sessions.	Legacy component; not recommended for use currently. If an opt-in block is setup within the journey, the participant will be able to opt-in to register for coaching sessions, which triggers this notification to run and send an intended admin or helpdesk with the details provided (usually by tokens) in the body of the email, likely including name, email address, program name, etc. The recipient of this is added to the Reply-To line of the notification configuration. This notification alerts the admin or helpdesk to use this information to load the user to the coachOS and enable coaching for the participant. This is meant to be used in scenarios where coaching is an optional added component and not meant for all the participants in the cohort to have access to. This is a very niche scenario and not common.	After
Action due	Committed to date by participant	Will send based on the due date committed to date by participant	Date can be pre-defined/fixed or selected by participant	Before
Go-Do	Select Individual Go-Do & Status: Committed; Behind; On-track; Is not completed; Completed; Abandoned	Sends based on the Status of the individual Go Do		Both
Cohort start	N/A	Cohort start date as per cohort config	Double check, is this correct or is it the date pax starts journey?	Both
Cohort end	N/A		Does this apply to, 1. Cohort end date, 2. Pax completing all content, 3. User expiry	After
User created	N/A	The date the user is created on the system	Do not use as an anchor for welcome emails if there is a possibility that the user already exists somewhere on momenta. Likely to be used for self-reg cohorts.	After
Coaching (Coaching Status)	Select Specific Session & Status: Unbooked; Greyed out; Booked; Missed; Completed	Sends to all participants where the relevant status condition is met for the specific Coaching session selected	To make this work you need to use it as if 0 days after works as “send now”.	After
Booking date (Coach OS session date)	All sessions	Send prior to every session on the journey, for every applicable participant	Will send related EACH Session on the journey.	After
Booking date (Coach OS session date)	Individual sessions	Sends prior to specific session, to all applicable participants	If you pick a specific individual session it will only send for that.	After
Stage Made Available	Identify the relevant anchor stage	Related to the static “make available” date for the stage in the journey or cohort blueprint. Cohort blueprint supersedes journey blueprint	Need to have a static “make available” date in the journey or cohort blueprint for the system to anchor to	Both
Module Made Available	Identify the relevant anchor module	Related to the static “make available” date for the module in the journey or cohort blueprint. Cohort blueprint supersedes journey blueprint	Need to have a static “make available” date in the journey or cohort blueprint for the system to anchor to	Both
Activity Made Available	Identify the relevant anchor activity	Related to the static “make available” date for the activity in the journey or cohort blueprint. Cohort blueprint supersedes journey blueprint	Need to have a static “make available” date in the journey or cohort blueprint for the system to anchor to	Both
Stage completed	Individual stages	The date on which the participant has clicked next through all activities within the given stage.	Does not necessarily mean that the activities embedded within have been completed.	After
Module completed	Individual modules	The date on which the participant has clicked next through all activities within the given module.	Does not necessarily mean that the activities embedded within have been completed.	After
Activity completed	Individual activities	If applicable, anything marked as compulsory within the individual activity must be marked as complete, and/or click next		After
Stage start	Individual stage	Related to the date the participant first clicks on any content in that stage		Both
Module start	Individual module	Related to the date the participant first clicks on any content in that module		Both
Activity start	Individual activity	Related to the date the participant first clicks in to the activity		Both
Action completed	N/A	The date on which the participant marks the action as complete	This is not the same as completing the activity in which the action is embedded	After
Team created	N/A	The date the team is created on the system		After
Secondary Condition Stage; Module; Activity;	Select specific stage, module, activity & Status: Completed; Is not completed	Used in addition to primary condition. For example IF Coaching session 1 is unbooked AND activity 1 is completed	Can be used with Static time AND dynamic time conditions. Functions as AND logic, no OR logic available	Both