Notifications: Architecture and Strategy
Follow

May 10, 2026 14:46

How notifications work in Continu — and how to use them to drive partner enablement, customer education, channel certification, and onboarding programs without burning out your audience's attention budget.

Why Notifications Matter

A learning program that no one notices is a learning program that no one does.

Notifications are the bridge between your system and your learner's attention. They are the moment a partner remembers their certification renewal is due. The nudge a customer admin gets that pulls them back into onboarding. The reminder a channel rep needs the day before a kickoff workshop.

Get them right and learners feel guided. Get them wrong and learners feel spammed — and once spammed, they tune out the next message, and the next, and the next. Every notification is a small withdrawal from a finite attention budget. Spend that budget badly and the whole program loses credibility.

This guide is about understanding what notifications actually are in Continu, and how to spend that attention budget wisely — especially with external audiences who have less patience for noise than employees do.

What a Notification Actually Is

In Continu, a notification is a message that fires in response to an event. Every notification has five attributes:

A trigger event. Something happened in the platform that the notification is responding to — an assignment was created, a due date is approaching, a workshop is starting, a certification is expiring, an admin pressed Send.
An audience. Who receives the message. Often a single learner, sometimes a Smart Segmentation rule, sometimes a manager or stakeholder rollup.
A channel. How the message gets delivered — typically email, sometimes in-app, sometimes both.
A template. The content of the message. May be system-defined (with limited customization) or fully custom.
Timing. When the message fires relative to the trigger. Immediately, a day in advance, on a recurring schedule.

Notifications come in two flavors: ones the platform sends automatically based on built-in events, and ones admins design and trigger themselves.

The Notification Architecture

Continu's notification model has three architectural layers worth understanding before you configure a single message.

System-generated notifications. These fire automatically when specific platform events occur. New assignment created. Due date approaching. Assignment completed. Workshop registration confirmed. Workshop starting in 24 hours. Certification expiring. The platform owns the trigger logic and provides the templates. You can typically edit the template content, the timing, and whether the notification is enabled — but the trigger event itself is fixed.

Custom notifications. These are admin-designed messages that fire on a trigger you choose. A launch announcement to a Smart Segmentation rule. A re-engagement nudge to inactive learners. A celebration message to learners who completed a Track. You own the trigger, the audience, the template, the timing — everything.

Notifications produced by automations. Most of the time, notifications and automations work together. An automation rule fires on an event (a new partner is activated), creates an assignment, and as part of the same flow generates a "you have a new assignment" notification. Architecturally, the notification is the side effect of the automation's action — not a separate rule.

The most useful mental model: every notification is the visible end of a longer chain. Trigger → segment evaluation → template render → channel delivery → learner engagement. Designing a good notification means designing all five steps deliberately.

What Can Be Edited and What Cannot

A common source of frustration: admins want to customize a notification and can't figure out which knobs they actually have.

Usually editable:

The body text of the message.
The timing relative to the trigger (e.g., "1 day before due date" vs. "3 days before").
Whether the notification is enabled or disabled.
The sender display name (within brand and platform constraints).
The audience scope, for custom notifications and notifications driven by automations.

Usually not editable:

The trigger event itself for system-generated notifications. You cannot easily change "new assignment notification" to fire on a different event — that event is built into the platform.
The underlying delivery infrastructure. Email goes through the platform's mail provider; you don't choose your own.
Some platform-mandated content for compliance or accessibility reasons (unsubscribe links in marketing channels, regulatory disclosures).

Always editable through deliberate design:

Whether to use a system notification at all. If you want a fully custom send, build a custom notification or an automation-driven message instead of trying to wrestle the system one into shape.

The strategic question: is what I'm trying to do achievable inside a system notification, or do I need a custom notification or an automation-driven message? If the answer is "custom," stop fighting the system one.

The Notification Lifecycle

Every notification moves through a five-step lifecycle. Understanding where each step can fail makes debugging easier.

Trigger. An event happens. The platform detects it.
Evaluation. The platform checks whether the notification's audience criteria match. For custom notifications scoped by Smart Segmentation, the segment evaluates here.
Template render. The message content is filled in with learner-specific data — name, content title, due date, link.
Channel delivery. The message goes out via email, in-app, or both. Email passes through the mail provider.
Engagement. The learner sees the message, opens it, clicks the link — or doesn't.

Failure modes by step: triggers can be misconfigured (wrong event); evaluation can target the wrong segment; templates can render with broken merge fields; delivery can fail silently (bounces, spam filters, blocked domains); engagement can drop because of fatigue, irrelevance, or untrustworthy sender reputation.

If a notification "isn't working," walk the lifecycle from trigger to engagement and find the broken step.

Common Notification Types and What Each Does

The notifications most learning programs rely on, organized by purpose:

Assignment lifecycle notifications.

New assignment. Sent when an assignment is created. Tells the learner what they have to do, by when, and provides a link to start.
Due-date reminder. Sent in advance of the due date. Cadence varies by program — typically 7 days before, then 1 day before for compliance-sensitive content.
Overdue. Sent when an assignment passes its due date without completion. Often paired with a manager-cc to escalate.
Completion confirmation. Sent when the learner finishes. A small but important moment — recognition signals that the learning landed and creates a positive memory of the platform.

Workshop notifications.

Registration confirmation. Immediate. Includes calendar invite, location/link, prerequisites.
Pre-workshop reminders. 7 days before, 24 hours before, 1 hour before for live virtual sessions.
Cancellation notice. When the workshop is cancelled or rescheduled.
Post-workshop follow-up. Recording (where applicable), slides, knowledge check, next steps.

Manager and stakeholder notifications.

Direct-report rollups. Weekly or monthly digests showing the manager their team's status.
Escalations. Specific alerts when a direct report is overdue or at risk on a critical assignment.
Partner manager rollups. Same logic, scoped to a partner manager's book of business.

Engagement and recognition notifications.

Re-engagement nudges. Sent to learners who haven't logged in or made progress in N days.
Recognition / celebration. Completion of a Track, achievement of a certification, milestone reached.
Cohort coordination. Updates to learners moving through a cohort program together.

Compliance escalation notifications.

Approaching due date (low intensity, learner only).
Past due (medium intensity, learner with manager-cc).
Significantly past due (high intensity, learner with manager and program owner cc).

Custom announcements. Launch communications, program changes, exec messages. Always scoped by Smart Segmentation to the audience that should care.

Best Practices — Cadence and Strategy

The single biggest notification design decision is how often to send. Too few and the program goes silent. Too many and the audience tunes out. The right cadence depends on stakes, audience, and content type.

Treat every notification as a withdrawal from the learner's attention budget. The budget is small. Spend it on messages that earn engagement. Each unnecessary notification reduces the value of the next necessary one.

Match cadence to stakes. A high-stakes compliance program can justify multiple reminders and an escalation. A low-stakes recognition message gets one send, never two. Internal employees tolerate more touches than external audiences. Partners and customers tolerate fewer.

Reminder timing — a starting framework.

Short content (under 30 minutes), low stakes: one reminder, 24 hours before due.
Medium content (a Track or a multi-step program): two reminders, 7 days and 1 day before due.
High-stakes compliance: three reminders, 14 days, 7 days, 1 day before due, with escalation if missed.
Workshops: registration confirmation immediately, 7 days, 24 hours, 1 hour. Past five touches per workshop you are training your audience to ignore you.
Renewals: 60, 30, 7 days before expiry. Consider a 14-day post-expiry final notice for compliance-critical certifications.

Compliance escalation cadence — three steps and stop. Past-due notice to the learner. Manager-cc on the second nudge. Program-owner-cc on the third. After three escalations with no response, the next move is a human conversation, not a fourth automated email.

Workshop reminder patterns deserve their own discipline. Live sessions have a much shorter attention window than asynchronous content. The hour-before reminder for a live virtual session is the highest-leverage notification you'll send for that workshop.

Brand the sender field carefully. External audiences see a name and a domain. If the name doesn't carry trust, the open rate drops. Use a sender that the audience already recognizes.

Coordinate across programs. A learner enrolled in three concurrent programs may receive nine notifications a week if you don't coordinate. Audit the total send volume per learner, not just per program.

Make every notification actionable. Every send should ask the learner to do exactly one thing — open this content, register for this workshop, confirm this completion. A notification with no action is noise.

Personalize where it earns its keep, generic where it doesn't. "Hi {first name}" is fine for most messages. Truly personalized recognition messages ("your 18th completion this quarter") are powerful but expensive — use them sparingly, when the moment deserves it.

Use executive visibility messaging deliberately. When an executive sponsor is the named sender on a launch, open rates jump. Save that lever for genuinely high-stakes moments. Overuse reduces it to zero.

Test before scaling. Send every new notification to a controlled test group of two or three users first. Verify it renders correctly, the merge fields populate, the sender is trustworthy, and the tone is right.

Anti-Patterns to Avoid

The notification mistakes we see most often:

Reminder fatigue. Five reminders per assignment. Three escalations per overdue. Daily nudges to re-engage. Past a threshold, every additional send reduces engagement on the next one.
Notifications without action. "Just letting you know" messages clutter the inbox without producing anything. Every send should ask the learner to do one thing.
Same message to everyone. A notification that lands the same way for partners, customers, and employees lands wrong for at least two of those three audiences. Scope by Smart Segmentation and tone the message accordingly.
Internal voice on external audiences (and vice versa). Casual employee tone reads wrong to a Tier 1 partner. Formal partner tone reads stiff to a new hire. Match the voice to the audience.
Notifying after the fact. A reminder sent the morning of a workshop the learner already missed teaches them not to trust your notifications.
Disabling all reminders to "reduce noise." Some teams over-correct from the fatigue problem and disable reminders entirely. The result: completion rates collapse. The right answer is fewer, sharper notifications, not none.
Manager-cc as the default escalation. Cc'ing a manager on every reminder turns the manager's inbox into noise. Reserve cc for genuine escalations.
Letting templates drift. A notification template written two years ago, referencing programs that have since retired, is actively harmful. Audit templates annually.
Skipping the post-completion message. The recognition send is the cheapest, highest-impact notification in the program. Skipping it is a missed opportunity.

Notifications in the Continu Architecture

Notifications connect to every other object in the platform.

Smart Segmentation defines who. Custom notifications and automation-driven notifications both scope their audience through a Smart Segmentation rule. Wrong segment, wrong audience.

Assignments drive the most notifications. Every assignment has a notification lifecycle attached — new, reminder, overdue, completed. The cleaner the assignment design, the cleaner the notification flow.

Workshops have their own notification rhythm. Registration, reminders, cancellation, post-session — all driven off the workshop state machine.

Automations produce notifications as a side effect. Most rule-driven notifications are not separate from the automation that creates the assignment — they are a built-in step in the automation's flow.

Reporting reads engagement signals from notifications. Open rates, click-through rates, send volume — all feed reporting.

A well-designed notification practice is sharp triggers + clean Smart Segmentation + appropriate cadence + tone matched to audience + action in every send + coordinated total volume + an annual template review. The platform handles delivery. Your job is to design the conversation.

External Audience Patterns

External audiences need careful notification design — they're harder to win and easier to lose.

Partner programs. Build notification cadences for partner activation (welcome + onboarding kickoff), certification renewal (60/30/7 day cadence), tier changes (immediate notice), and partner-manager rollups (weekly or monthly digest). Avoid daily nudges. Use a sender name your partners recognize as a partner-program contact, not a generic system address.

Customer education. Customer admins are typically time-poor and inbox-overloaded. Design notifications around real moments — onboarding kickoff, key adoption milestones, renewal windows. Avoid completion confirmations that feel patronizing. Coordinate with the customer success team's communication cadence so customers don't get hit twice.

Channel programs. Channel reps move between brands and have multiple vendors competing for their attention. Your notifications need to earn their place. Lead with what matters to the rep's quota or certification status. Avoid corporate-sounding announcements; channel partners tune those out.

Franchisees. Franchise operators are operating businesses, not employees. Treat their attention like a customer's. Reserve notifications for operational and compliance events; route everything else through their franchise system of record.

A note on tone for external audiences. Internal cultural references, in-jokes, and casual sender names that work for employees can feel off-brand to a partner or customer. When in doubt, lean slightly more formal for external sends.

Internal Audience Patterns

Internal notifications are more forgiving than external ones — but the principles still apply.

New hire onboarding. Welcome message, weekly progress reminders, manager rollups.
Compliance reminders. Date-based, escalation pattern as above.
Manager nudges. Weekly direct-report rollups, escalations on overdue.
Recognition messages. Track completions, certifications, anniversaries.
All-hands announcements. Custom notifications scoped to the full employee segment, used sparingly.

Internal audiences will tolerate more notification volume than external ones — but only modestly more. The same principle applies: every send should earn its place in the inbox.

Known Behaviors and Limits

A few things worth knowing in advance:

Email delivery depends on infrastructure outside Continu. Your notification went out from Continu, but whether it arrives in the learner's inbox depends on their domain, their mail provider's spam filters, and the platform's sender reputation. If a specific domain is reporting non-delivery, check with their IT team.
Notifications fire on event timing, not on a daily batch schedule. A new assignment notification typically goes out within minutes of the assignment being created. Workshop reminders fire at the configured offset from workshop start time.
Disabled or inactive users do not receive notifications. A user marked inactive or terminated in your source system will not receive sends, even if their assignment state would otherwise trigger one.
Localization may apply, depending on configuration. Some templates support multi-language rendering based on the learner's preferred language. Confirm what your team has configured.
Bulk custom notifications take time to send. A custom notification scoped to 50,000 users does not all leave the platform instantly. Plan launches with delivery time in mind.
Unsubscribe behavior varies by notification type. Compliance and operational notifications typically cannot be unsubscribed from. Marketing-style sends usually can. Confirm before relying on a specific behavior.
Test sends behave differently from live sends. A test send to your own address is not a complete proof that the live send will work — segment evaluation, deliverability, and tracking can all differ. Treat tests as a sanity check, not a guarantee.

Notifications: Architecture and Strategy Follow