Notifications
Choose which operational events notify a user by email: conversation starts, contact capture, and message feedback.
Check which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
What Notifications is for
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 this page to identify what the control changes, which source context it uses, who owns the result, and where to verify it.
Use the page to identify the trigger, source data, owner, visible result, and review point before changing production behavior.
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.
Start with one workflow, message, record update, or Max task before expanding. The team should know what changed, who owns it, and how to pause or adjust it.
Troubleshooting
If the result is wrong, debug in this order: source data, permissions, connected tools, required fields, workflow logs, then any generated output used later.
When debugging, open the related CRM record, Max activity, workflow run, or integration log first. Fix the source data or rule before adding more automation.
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.