Alerts, SSL & status page

Get told the moment something breaks - on the channels your team actually watches - and give your users a page to check.

Set up notifications end to end

You'll be alerted the moment a monitored journey or page breaks, on email, Slack, and Discord - each alert carries a screenshot of exactly what a visitor saw. Here's the whole flow, start to finish.

1. Pick the site. Notifications are configured per site (the switcher at the top of Settings), so an agency can route each client's alerts to a different place. Choose the site you want to set up, then hit Edit.

2. Add where alerts go. Under Settings → Notifications:

• Email - type one or more recipient addresses (comma-separated).
• Slack (Starter and up) - toggle on and paste a Slack Incoming Webhook URL (see below).
• Discord (Starter and up) - toggle on and paste a Discord Webhook URL (see below).

You can enable any combination - all enabled channels get the same alert.

3. Choose severity. Alert Severity decides what actually pings you:

• Critical only (default) - only critical incidents alert. Warnings still open an incident on your dashboard, quietly.
• All issues - warnings alert too.

Mark your important flows (checkout, booking, sign-up, homepage) as Critical so they page you; leave nice-to-haves as Warning.

4. Save. That's it - no API keys or bot tokens anywhere. The webhook URL is the credential.

5. What you'll receive. When a Critical journey or page fails - and only after SiteOps re-checks it a few times to rule out a blip - you get one alert with:

• a plain-language title and what a visitor experiences (no raw error codes),
• the screenshot of the broken screen embedded right in the email body and in the Slack/Discord message,
• a link straight to the incident, and what to check.

Then an escalating reminder at 2h and 24h if it stays broken, and an "all clear" when it recovers - never per-check spam. A recovered incident moves to your Resolved tab with before/after screenshots.

Test your alerts

Confirm the whole pipeline in a couple of minutes:

1. In Journey Map, build (or open) a journey and hit ▶ test so it shows ✓ Verified. A verified journey is treated as proven, so it alerts on its next real failure per its severity.
2. Set that journey to Critical and make sure at least one alert channel is configured for its site (step 2 above).
3. Trigger a failure - e.g. point a step at something that will break, or temporarily take the page offline.
4. Within a few minutes (after the confirmation re-checks) you'll get the alert on every enabled channel, screenshot included, and an incident opens on the dashboard.
5. Fix it (or let it pass) and the next successful run auto-resolves the incident and sends the recovery notice.

Setting this up for a client to try? Do steps 1-4 on one of their real flows, then show them the alert that lands - the embedded screenshot of their own broken checkout is the fastest way to prove the value.

Alert channels

Configure these in Settings → Notifications.

No API keys or bot tokens are needed - the webhook URL is the credential. Just paste it and save.

Plan note: Email works on every plan (the recipient limit scales by tier: Free 1, Starter 3, Pro 5, Agency 15, Enterprise unlimited). Slack and Discord alerts are a paid feature - Starter and up - on Free those toggles are disabled with an Upgrade prompt.

SiteOps automatically confirms a failure across several re-checks before it alerts (built in - there's no "alert after N failures" setting to tune) and respects an alert cooldown, so you get signal, not spam. When an incident opens you get one alert, then an escalating reminder at 2 hours and again at 24 hours if it's still broken, and a recovery ("all clear") alert when it's fixed - never per-check spam. You can also enable a weekly report summarizing uptime and incidents.

Alert severity controls what reaches your channels: Critical only (the default) sends only critical incidents; All issues also sends warnings. Critical always alerts on every enabled channel.

Getting a Slack webhook

1. In Slack, create (or open) an app → Incoming Webhooks → Add New Webhook to Workspace.
2. Pick the channel, copy the URL (starts with https://hooks.slack.com/…).
3. Paste it into SiteOps → Notifications → Slack, enable, save.

Getting a Discord webhook

1. In Discord: Server Settings → Integrations → Webhooks → New Webhook.
2. Choose the channel, Copy Webhook URL.
3. Paste it into SiteOps → Notifications → Discord, enable, save.

SSL & domain-expiry warnings

SiteOps runs a daily sweep of your monitored sites' TLS certificate and domain registration and warns you well before either expires - the kind of outage that has nothing to do with your code and everything to do with a forgotten renewal.

• Ask any time: when does my SSL and domain expire?
• Or let the sweep alert you through your configured channels.

Public status page

Give your users a page they can check during an incident.

• Each status page has a slug, served at a public URL (e.g. status.siteops.vubex.dev/your-slug).
• It shows current status and recent uptime for the sites you choose to make public.
• Enable and name it in your settings.

Tip: link your status page from your app's footer or error pages so customers self-serve during an incident instead of flooding your inbox.

Next: the buttons and screens themselves - UI elements.