Notifications

Documentation Index

Fetch the complete documentation index at: https://docs.onsomble.ai/llms.txt

Use this file to discover all available pages before exploring further.

Onsomble can notify you about a range of events. The goal is to keep you informed enough to act on what matters, without generating so much noise that you start ignoring the notifications entirely. This page explains what Onsomble can notify you about, where those notifications arrive, and how to tune the mix so it stays useful.

​

What Onsomble notifies you about

Notifications fall into four broad categories.

​

Scan events

• Scan completed — a scheduled or ad-hoc scan has finished and results are ready
• Scan failed — a scan couldn’t complete (connection issue, model error, timeout)
• Significant change detected — a scan finished with a meaningful movement compared to the previous one (a big drop in citation, sentiment going negative, a new competitor appearing prominently)

​

Workflow events

• Workflow error — a published workflow hit a runtime issue the business needs to know about
• Unusual drop in usage — a workflow that’s been getting regular traffic has stopped being invoked, suggesting something may be broken
• New high-impact usage pattern — a customer pattern worth noticing (e.g. a specific step suddenly seeing high drop-off)

​

Connection events

• Connection broken — the bridge between the business website and Onsomble has stopped verifying, which means AI assistants can no longer discover workflows or knowledge
• Ingestion failed — a re-ingestion couldn’t complete

​

Account events

• Plan or billing changes — payment failures, upcoming renewals, approaching plan limits
• Team access changes — someone was added to or removed from a Site
• Invitation accepted — someone you invited has joined

​

Where notifications arrive

Notifications show up in three places:

• Email — the default for most events. Lands in your inbox at the email address on your account.
• In-app — visible in the notification panel at the top of the Onsomble dashboard. Clicking through takes you directly to the relevant Site or workflow.
• Portfolio dashboard flags (agency only) — attention-needed signals surface on the portfolio dashboard itself so you see them during normal triage even without an email.

You can choose which channel carries which notification. For example, many users keep scan-completion notifications in-app only and reserve email for failures and significant changes that need quicker attention.

​

Configuring notifications

From Account settings → Notifications, each notification type has three settings:

• On / off — whether the notification is sent at all
• Channels — email, in-app, or both
• Threshold (for change-based notifications) — how significant a change needs to be before you’re notified

Configuration applies per user. Each team member tunes their own preferences — your choices don’t affect anyone else on the team.

​

Notification strategy for single businesses

For Sam — a business owner managing one or two Sites — a sensible default:

• Email: scan completion, scan failure, connection broken, significant change, billing events
• In-app: everything else — team changes, workflow usage patterns, invitations

That keeps the inbox interesting only when something needs attention, while still surfacing richer context when Sam actually logs in.

​

Notification strategy for agencies

For Maya — an agency managing 20+ clients — the equation changes. Every client generates events. Getting an email per completed scan across thirty clients a week means thirty emails no-one reads. A practical pattern:

• Portfolio dashboard flags only — for routine events like scan completions. You see them during your daily portfolio triage instead of as individual notifications.
• Email — reserved for exceptions: scan failures, broken connections, significant change detections, and any workflow errors. These are the events that might need action before your next scheduled triage pass.
• Per-client filtering — for very active clients, you may want more granular notifications. For lower-touch clients, less.

The portfolio dashboard was designed to absorb the routine volume so your inbox stays clean.

​

Tuning significant-change thresholds

Change-based notifications (citation drops, sentiment shifts, competitor gains) depend on a threshold — how big does the change need to be before we tell you? Set the threshold too low and you’ll be notified on every scan regardless of whether anything actually matters. Set it too high and you’ll miss meaningful movements. Onsomble’s defaults are tuned to surface changes worth a human look, but adjust them if you find yourself either ignoring or missing alerts.

​

When to review your settings

A few moments when it’s worth revisiting notification settings:

• First week of onboarding a client. You’ll want more frequent updates early on, fewer once the picture stabilises.
• After a portfolio grows by a lot. The notification mix that worked for 5 clients is probably noise at 25.
• When you notice yourself ignoring emails from Onsomble. That’s the clearest signal the mix is off.

Think of the settings as tuning, not as set-once-and-forget. A few minutes of adjustment every couple of months keeps the signal-to-noise ratio where it should be.