Expanded Systems Reference
Notifications
Targeted alerts from workflow state and agent judgments.
Summary
Where this system fits.
Secondary reference material for teams and crawlers that need more detail than the public navigation exposes.
What It Is
Notifications turn Secure CDM state, workflow events, and agent judgments into timely email, SMS, or customer-owned message delivery.
What It's For
Targeted alerts from workflow state and agent judgments.
Why It's Needed
Operational blockers often stay hidden until someone manually checks a report, sends a follow-up email, or receives an escalation call.
Reference Detail
Operational shape.
Who Uses It
- Finance teams
- Project operations teams
- Administrators
- Approvers
- External workflow participants when approved
Inputs
- Workflow events
- Secure CDM status
- Exception states
- Agent judgments
- User roles and routing rules
Processing
- Detects relevant events and status changes
- Routes messages to the right people
- Supports triggered and scheduled sends
- Keeps alerts tied to workflow context
Human Controls
- Routing rules
- Role-based recipient lists
- Review of sensitive message content
- Opt-in and operational messaging boundaries where applicable
Security and Privacy Notes
- Messages should include only the context needed for action
- Sensitive workflow details should remain behind approved access controls
- Delivery can use Big Robot-managed or customer-owned email and SMS platforms
Outputs
- Email notifications
- SMS notifications
- Scheduled reminders
- Triggered workflow alerts
Integrations
- Secure CDM
- Web Controls
- Email platforms
- SMS platforms
- Customer-owned notification systems
Implementation Pattern
- Identify the workflow moments where earlier action prevents delay.
- Define who needs the alert and what action they should take.
- Keep message content narrow and link back to controlled workflow surfaces when needed.
Results or Expected Outcomes
- Earlier action on blockers
- Less manual follow-up
- Cleaner handoffs between teams
- Fewer noisy alerts because routing is tied to workflow state
When to Use
- A workflow depends on timely action from specific people
- Manual follow-up creates delay
- Status changes should trigger review or action
When Not to Use
- The workflow already has reliable notification rules
- The message would expose sensitive information to the wrong audience
- The alert has no clear recipient or action
Related Systems
FAQ
FAQ
Are notifications just reminders?
No. They are tied to workflow state, exception conditions, agent judgments, and routing rules so they prompt the right action at the right time.
Can Big Robot use customer-owned messaging platforms?
Yes. Notification delivery can be Big Robot-managed or connected to customer-owned email and SMS platforms.