Prove
Alerts and inbox
Get told when something important changes, tune what counts as important, and clear every decision waiting on you from one list.
Rixe checks your data every night so you do not have to open every screen every day. Two places collect what it finds. Alerts records what changed — a significant score move, a rival surging, a new influential source, an engine that could not be measured. Inbox holds what is waiting on your decision — content to approve, messages ready to send, suggested competitors and prompts. Read alerts to know; clear the inbox to act.
Where to find them
Click the bell (Notifications) at the top of the app. It shows Inbox and Alerts, each with its count, and the badge on the bell is the total. You can also go straight to https://app.rixe.ai/alerts and https://app.rixe.ai/inbox, or search for either with Find anything….
Alerts
Reading the list
The Alerts screen has two tabs: Alerts (the list) and Thresholds (the rules).
At the top, Unread and This week (last 7 days) count your alerts, and a line repeats the newest unread one. Filter the list with All / Unread and by alert type. Each alert shows:
- a type badge, coloured by urgency — red stops data or needs action now, amber needs a look, green is a recovery;
- the logo of the engine, domain or competitor it is about;
- whether it left as an email (E-mailed · date) or stayed in the app (Panel only);
- a control to mark it read or unread.
Two buttons sit in the page header. Mark all as read clears the unread count. Rescan runs the checks now instead of waiting for the night.
Alerts are a record
Everything Rixe finds stays on this screen. Turning off email or Slack for an event only silences the delivery; it does not delete the alert.
Alert types
| Type | When it fires |
|---|---|
| Significant change | Your mention rate on an engine over the last 7 days differs from the 7 days before by at least 10 points, and the change is statistically significant (p < 0.05). Either test alone produces alerts you cannot act on. |
| Competitor surge | A rival's share of voice rose by at least the threshold (default 15 points) in seven days. |
| New source | A domain not seen before is cited in at least the threshold number of prompts (default 3). |
| Citations stopped | A source that had cited you at least 3 times stopped citing you entirely. A fall to zero only — smaller dips are noise. |
| Engine down / Engine recovered | An engine could not be measured, and when it is measured again. While it is down its data is marked missing, never counted as zero. |
| Measurements not completing | An engine's measurements stayed unfinished for hours past their due time. No data is being collected while this is true. |
| Misinformation | The same false claim about your brand appeared on at least the threshold number of engines (default 3). See Misinformation. |
| Refresh candidate | A page of yours is a strong candidate for a refresh. |
| Budget | Monthly spend reached 80% and 100% of its limit. |
| Workflow | A workflow's notify step sent a message, with the severity the step was given. See Autopilot and workflows. |
Content and report notices (for example a comparison brief that is ready) also appear in the list.
Thresholds
Open the Thresholds tab to tune when the rules fire for this workspace. Defaults come from your market's pack; a value you change is marked customised and applies only to this workspace.
| Field | Meaning |
|---|---|
| Competitor surge (points) | We warn you when a competitor's share of voice rises by this many points in seven days. |
| New source (number of prompts) | We warn you when a domain we have not seen before is cited in at least this many prompts. |
| Misinformation (number of engines) | We escalate when the same false claim appears on this many engines. |
| Minimum measurements | Below this many measurements no rule fires — a small sample raises nothing. |
Click Save. The message "Thresholds saved. Tonight's check will use these." confirms it; use Rescan to apply them straight away.
Choosing where alerts go
Which events leave the app, and by which channel, is set for the whole organisation under Settings › Notifications in the Notification matrix. The in-app bell is always on; E-mail, Slack and Webhook are chosen per event. Only owners and admins can change it.
| Event | Default channels besides in-app |
|---|---|
| Significant change | E-mail, Slack, Webhook |
| Budget | E-mail, Slack |
| Engine degraded | |
| Integration broken | |
| Misinformation | E-mail, Slack |
| Autopilot | E-mail, Slack |
| Workflow | None (each workflow's own notify step decides) |
Slack needs a webhook address under Settings › General, and webhooks need an endpoint under Integrations. Personal e-mail preferences apply on top. See Webhooks and Team and roles.
Inbox
The Inbox is the single queue of decisions waiting on you, grouped by what the decision does rather than which page produced it. Work that is not listed here is work the system runs on its own.
| Group | What approving does | Buttons |
|---|---|---|
| Autopilot jobs | Prepared by the system; leaves for the outside world once you approve. Each shows its risk: your site, your account or third party, and when it is due. | Approve / Decline |
| Playbook decisions | A rule fired; approval starts paid generation. | Approve / Decline |
| Content awaiting review | A draft is ready; approval queues it for publishing. Approval can be refused if a claim check fails. | Approve |
| Briefs awaiting approval | A page plan from a measured gap; approval writes the draft. | Generate content |
| Messages ready to send | Draft and recipient are ready; sent on your behalf. | Send / Decline |
| New competitor suggestions | Brands named beside you in at least 5 answers that you do not track yet. | Add as competitor / Dismiss |
| This week's prompt recommendations | From coverage gaps, market demand and site searches; accepting starts tracking. | Accept / Dismiss |
| Misinformation to verify | Claims the engines made that you believe are wrong. | Approve / Not valid |
| Recommended actions | The top-scored recommendations from the nightly engine (up to five); the full list is on the action plan. | Plan / Dismiss |
Every row also has Review, which opens the item on its own screen. After a decision the row shows Done. A group with more items than fit shows +N more, which opens the full list.
Clearing the inbox, step by step
- Open the bell and click Inbox.
- Start at the top: Autopilot jobs and Messages ready to send are the ones that leave Rixe.
- For each row, click Review if you need the detail, then decide.
- Work down to Recommended actions, or click Go to actions to see the whole plan. See Action plan.
When nothing is waiting, the Inbox says so. New items appear as the nightly jobs and the weekly recommendations produce them.
Limits and availability
Alerts, the notification matrix and the inbox are included in every plan. Sending to the outside world through autopilot depends on your plan; see Autopilot and workflows and Plans and limits.
Roles matter: viewers can read alerts and the inbox but cannot mark alerts, change thresholds or rescan; owners, admins and members can. Only owners and admins edit the notification matrix.
Common questions
I see no alerts. Rules need data: a comparison needs at least two measurements, and no rule fires below the Minimum measurements threshold. A new workspace stays quiet for its first days. Use Rescan to check immediately.
I was not e-mailed about an alert. Check the badge on the alert: Panel only means the event is not set to e-mail in the notification matrix, or your personal e-mail preferences turned it off.
An engine-down alert came in. Did my score drop? No. While an engine cannot be measured its data is marked missing and shown with a badge; the score is not silently lowered. An Engine recovered alert tells you when the gap ends.
Related pages
Still stuck? Write to [email protected] and a person will answer.