Notifications

Overview#

Notification preferences control what Seerly emails you about, and how often.

AI visibility moves slowly, and notifications ought to reflect that. They are meant for the handful of things genuinely worth interrupting you over, rather than functioning as a feed you check.

Interpreting results#

Preferences are set per person rather than per project, so everybody on the team chooses their own. That matters more than it sounds, because the person fixing site issues and the person writing content have almost no overlap in what they need to hear about.

Subtypes let you be selective inside a category, so you can take completion notices without receiving every incremental update along the way. Turning something down is not the same as turning it off, and the middle setting is usually the one people actually want.

Unsubscribing from one thing also does not unsubscribe you from everything. Account and billing messages sit outside product notifications and carry on regardless of what you set here.

Best practices#

The only real measure is whether you read them. The most common failure is subscribing to everything, learning within a fortnight to ignore all of it, and then missing the one message that actually mattered.

Sensible defaults for most people:

• Analysis completed, so you know when there is something new worth looking at.
• Agent output awaiting approval, which is genuinely time-sensitive since agent findings decay.
• Significant changes, meaning the ones worth being interrupted for.

Reasonable to turn off:

• Routine progress updates, which you can see in the dashboard whenever you choose to look.

Next steps#

1. Set your preferences once, early. The defaults are a starting point rather than a recommendation for your particular situation.
2. Give different roles different settings. Implementers do not need content notifications and writers do not need audit ones.
3. Turn down rather than off wherever a subtype exists.
4. Revisit if you notice yourself ignoring them. Ignored notifications are worse than none at all, because they train you straight past the important ones.

How notifications fit the rhythm#

AI visibility runs on a weekly rhythm, and notifications are how the product respects that instead of demanding a daily login. A working setup lets you close the dashboard with confidence: the run-complete notice tells you when there is genuinely something new, the approval notices carry the one kind of output that decays if it waits, and everything else holds until your weekly pass.

The test of your configuration is a quiet fortnight. If two weeks pass and every email you received was either acted on or genuinely informative, the setup is right. If you deleted most of them unread, turn those categories down before you learn to delete the important ones too, and if you found yourself checking the dashboard "just in case", turn the completion notices back on, because that itch is the exact thing they exist to remove.

Limitations#

Notifications tell you that something changed. They are not the analysis; the dashboard is.

Account, billing and security messages are not product notifications and are unaffected by anything you set here.