Notifications
Choose which operational events notify a user by email: conversation starts, contact capture, and message feedback.
Use this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Learn the system by following the product states.
Use the screenshots as the primary map: start with the full context, trace the connected workflow, inspect the focused UI, then compare against the completed operating state.
Visible controlAccess or policyOperational effectUse this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Summary
Choose which operational events notify a user by email: conversation starts, contact capture, and message feedback.
Concepts covered
Step breakdown
- Open NotificationsStart in the Notifications section of the Admin control center.
- Inspect the real controlsIdentify the visible fields, buttons, switches, tables, and menus before changing configuration.
- Connect the setting to operationsUnderstand which user access, customer memory, developer access, usage, billing, or data-model behavior this setting affects.
What this screen does
Notifications decides which product events should reach the operator by email. The screen shows a master Notifications switch, event-level switches, an Email delivery column, and Save.
The captured event types are Conversation Started, Contact Capture, and Message Feedback. Each row represents a signal that may require human awareness or follow-up.
What each control changes
The master switch enables or disables notification behavior. Event switches decide whether that specific event should notify the user. Email checkmarks show the delivery channel. Save persists the notification policy.
Operators should enable the events they are responsible for reviewing. A support owner may care about new conversations; an operations lead may care more about captured contacts and message feedback.
Operational outcome
Good notification settings make review visible without turning every event into noise. The goal is timely human attention for important operational signals.
Operational playbook
Use Notifications as part of the Frontline Admin Notifications operating loop: inspect the current product state, confirm the source context, and decide what should happen next.
The goal is not to memorize screens. The goal is to understand how the product surface supports repeatable work, AI assistance, and accountable handoff.
Best practices
Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.
Prefer narrow, inspectable setups over broad automation. Teammates should be able to explain why the system took an action from the visible product state.
Troubleshooting
If the result does not match expectation, check the source context first, then permissions, connected integrations, required fields, workflow logs, and any AI-generated output used by downstream steps.
When in doubt, compare the latest product state with the related record, activity, or workflow execution so debugging starts from evidence rather than guesswork.
FAQs
What does Notifications control?
Choose which operational events notify a user by email: conversation starts, contact capture, and message feedback.
Who should use this page?
Workspace admins, implementation owners, and operators responsible for configuring access, account behavior, developer integrations, or the data model.
How should this page fit into onboarding?
Use it to understand the product surface, inspect real UI states, and connect the concept to daily operating workflows before configuring production behavior.
What should I verify before using this in production?
Verify ownership, permissions, source context, failure behavior, and the handoff path so teammates can trust what the system does next.