Notifications
Objective. Explain notifications and alerts as the platform's way of surfacing what needs attention when it needs it, so you can position timely action honestly - and keep 'an alert fired' distinct from 'a problem was confirmed and resolved'.
Notifications are how the platform makes insight timely rather than retrospective. This teaches what alerts do in Time Champ terms, what is safe to say, and the interpretation discipline that an alert is a prompt to investigate, not a confirmed problem or a completed action.
See it in the demo
What notifications are in Time Champ terms
A notification surfaces something that needs attention while there is still time to act on it. The demos show this most clearly in the real-time and intraday apps: Intraday Management raises alerts when the day drifts and pairs them with actions; Real-Time Adherence surfaces exceptions as they happen; across the suite, exceptions and recommendations draw a manager's eye to where investigation is warranted.
The honest framing is that notifications turn the platform from a rear-view report into a timely prompt. But a notification is exactly that - a PROMPT. It says 'look here', not 'this is confirmed' or 'this is fixed'. That distinction is the same discipline as every other metric in the Academy: the signal invites investigation, it does not deliver a verdict (F04, F06).
What a Sales or CSM person can say confidently
Safe to say: 'The platform surfaces what needs attention when it still matters - intraday alerts when the day drifts, adherence exceptions as they happen, recommendations where a manager should look - so action is timely, not retrospective.'
Safe for CSM operating routines (C06): build the manager routine around responding to exceptions and alerts, with the response time and reviewed-exception rate as the measures that show the routine is working (rta/idm candidate measures).
Safe as an interpretation rule: an alert is a prompt to investigate, not a confirmed problem; and an alert firing is not the same as the issue being resolved - the action log and outcome show resolution (PLAT-13).
Do not assert the exact notification channels (email, in-app, mobile, integrations), delivery reliability, or configurability for a specific customer - those are product and configuration facts.
What always escalates to security or product
Route to a specialist:
- Which notification channels are available (email, in-app, mobile, chat/collaboration integrations) for a given customer.
- Delivery reliability, timing guarantees and escalation/routing logic.
- How notifications are configured, throttled and targeted to roles.
- Any notification delivered through an external system (overlaps PLAT-08) or containing sensitive data (overlaps PLAT-06).
The posture: that the platform surfaces timely alerts and exceptions is demo-supported; the channels, delivery guarantees and configurability for a given customer escalate.
The honest limit
Demo-supported: the platform raises intraday alerts, surfaces adherence exceptions in real time, and presents recommendations and exceptions that direct attention.
Confirm with product: available channels, delivery reliability and timing, configurability and routing, and any externally delivered or sensitive-data notification.
Separate cleanly: 'the platform surfaces what needs attention when it matters' (safe) from 'alerts are delivered to this channel, reliably, within this time, configured this way' (confirm with product). And always hold the interpretation line: an alert is a prompt, not a confirmed problem or a completed fix.
Interpretation check
A notification is a prompt to investigate, not a confirmed problem; and an alert firing is not the same as the issue being resolved. Timely surfacing is demo-supported; channels, delivery guarantees and configurability are product confirmations.
Practical task
Using the Intraday Management and Real-Time Adherence demos, design a manager alert-response routine: which alerts and exceptions the manager watches, the response-time and reviewed-exception measures, and the sentence that keeps the team from treating an alert as a confirmed problem. List the channel and delivery questions you would route to a specialist.
Self-check
What is the honest value of notifications in one sentence?
They surface what needs attention while there is still time to act - intraday alerts, real-time exceptions, recommendations - so action is timely rather than retrospective.
Why is 'an alert fired' not the same as 'the problem is fixed'?
An alert is a prompt to investigate, not a confirmed problem or a completed action; resolution is shown by the action log and the verified outcome, not by the alert itself.
A customer asks which channels alerts come through and how reliable delivery is. What do you do?
Confirm that the platform surfaces timely alerts and exceptions, then route channels, delivery reliability and configurability to a specialist.
Which notification facts are safe and which escalate?
Safe: that intraday alerts, real-time exceptions and recommendations surface attention, and the prompt-not-verdict interpretation rule. Escalate: channels, delivery reliability/timing, configurability/routing, and external or sensitive-data delivery.
Verified vs demo. Timely intraday alerts, real-time adherence exceptions and attention-directing recommendations are shown in the demos; available channels, delivery reliability and timing, configurability and external delivery are product facts to confirm.