Notification channels

Choose how you want to be told when something goes wrong.

Overview

When DomainDash confirms a problem with one of your sites, it can reach you by email, SMS, Slack, a webhook, or any combination. Which channels you have depends on your plan:

Channel	Available on	What it's for
Email	All plans	Every notification, with per-member category control
Slack	Starter, Pro, Business	Incidents, billing, and team activity routed to channels
SMS	Pro, Business	Incident alerts and their recovery, per member with plan SMS seats
Webhooks	Pro, Business	Signed JSON sent to your own endpoints

The trial includes SMS too, limited to 1 seat and 10 texts a month.

For setting up Slack, see Slack integration. For SMS, see SMS notifications.

DomainDash sends five kinds of notification:

Notification	When it's sent	Channels
Urgent alert	A P0 (Urgent) incident is confirmed: your site is Down, or a page failed its content check	Email, SMS, Slack, webhooks (site-down incidents only)
Ongoing updates	Periodically during an active P0 incident	Email
Resolved	A P0 incident has been resolved and your site is back to normal	Email, SMS, Slack, webhooks
Daily digest	Each morning, around 9am in the team owner's timezone, if non-urgent incidents are open	Email, Slack (Starter and above)
Weekly summary	On Monday mornings, around 8am in your own timezone	Email

By email, SMS, and Slack, only Urgent incidents alert you immediately. Needs fixing, Needs a look, and Worth knowing incidents appear in the app and in the daily digest. Webhooks are separate: DomainDash sends webhook events as soon as an incident opens, whatever its severity.

Setting up email notifications

Email notifications are on from the start. As soon as you create an account and add a site, alerts go to the email address you signed up with.

1. Verify your email address

   DomainDash sends alerts, digests, and billing emails whether or not you've verified your address. Until you do, a banner reads "Please verify your email address." with a Resend email action.

2. Choose your categories

   Choose which categories you receive (Incidents, Billing, Team activity, and Weekly summary) on the Your notifications page (avatar → Profile → Your notifications). You can opt out of any of them. You choose within the categories a team owner or admin has switched on for you: the email panel on Settings → Notifications is the team-wide matrix where owners and admins set each member's ceiling.

3. Check your spam folder

   If you're not receiving notifications, check your spam or junk folder. Adding inbox@domaindash.io to your contacts can help.

The other channels

• Slack posts rich messages into the channels you choose, with per-category routing. See Slack integration.
• SMS texts members when a site goes Down and when it recovers. SMS is per-user: each member verifies their own mobile number, and the team has a set number of SMS seats from its plan. See SMS notifications.
• Webhooks send a signed JSON payload to an endpoint you control, so you can wire incidents into your own tools. Set them up on Settings → Developers.

How each notification works

Urgent alerts

When a P0 (Urgent) incident is confirmed, DomainDash alerts your team, usually within a couple of minutes on a paid plan, and around six minutes on the Free plan. The email says what's wrong and which site is affected, and links to your dashboard. If your plan includes SMS, members with a verified number and a seat get a text too. If Slack is connected, the alert is posted to your Incidents channel. For site-down incidents, any configured webhooks fire. (A failed content check reaches you by email, SMS, and Slack but sends no webhook event, though its recovery does.)

If several sites go Down together, your team gets one combined alert covering them. Resolved notifications are sent per incident.

Ongoing updates

During an active P0 incident, DomainDash emails your team periodic updates. They start shortly after the incident is confirmed and become less frequent as the incident continues.

Each update includes how long the incident has lasted and how many checks have failed. They stop when the incident is resolved.

Daily digest

Each morning, around 9am in the team owner's timezone, DomainDash checks whether you have any open non-urgent incidents. If you do, it sends a summary by email and, on Starter and above, Slack. The summary lists each incident, grouped by severity:

• Needs fixing: SSL certificate expired or invalid, DNS failing, domain name expired
• Needs a look: site responding slowly
• Worth knowing: SSL certificate or domain name expiring soon

Each item shows how long the incident has been open.

Weekly summary

On Monday mornings, around 8am in your own timezone, DomainDash emails a weekly summary. It's email only, and it's on by default for owners and admins.

Resolved notifications

When a P0 incident is resolved, for example your site comes back up or a page starts passing its content check again, DomainDash sends your team a follow-up. It tells you which site recovered, what the problem was, and how long it lasted.

Who gets notified?

DomainDash notifies the members of the team that owns the affected site. If you're part of multiple teams, you'll only receive notifications for sites belonging to the teams you're a member of.

Email has two layers, and both must be on. A team owner or admin sets the team-wide ceiling (for example, switching a category off for a member) and each member chooses within that. So incident emails reach every member by default, but a member won't get them if an owner or admin has switched them off for that member, or the member has opted out. A member with an SMS seat is switched on for texts straight away and can switch them off.

Managing your notification settings

Notification settings are spread across three pages:

• Your notifications (avatar → Profile → Your notifications): choose your own email categories, and switch SMS off or back on (once an owner or admin has given you a seat)
• Settings → Notifications (owners and admins only): set the team-wide email matrix (each member's category ceiling) and assign SMS seats
• Settings → Integrations (owners and admins only): connect Slack and route each category (Incidents, Billing, Team activity) to a specific channel

You verify or change your own mobile number on your profile.

Related

• SMS notifications for a step-by-step SMS setup guide
• Slack integration to post alerts into your team's Slack channels
• How incidents work for how DomainDash detects and confirms problems
• Site settings to customise how DomainDash checks each site