Email alerts for downtime: boring, reliable, still essential
Chat apps are fast, but email remains the audit trail. SitePuls sends incident email through alert contacts you configure—use it for on-call inboxes, ticketing systems that ingest mail, or leadership digests.
How email contacts work
You add verified email addresses as contacts, attach them to monitors, and failures notify those addresses.
Compared to Telegram
Telegram is synchronous; email is asynchronous and archivable—many teams use both.
Compared to webhooks
Email is human-friendly; webhooks are automation-friendly—route by severity.
Spam and filtering
Allowlist SitePuls sender domains in your mail stack so alerts do not land in junk during outages.
Multiple recipients
Create separate contacts or distribution lists according to your process.
Testing contacts
Use built-in test tools where available to confirm delivery before a real incident.
What SitePuls does not do
Dedicated SMS gateway or voice dial-out—email and other channels supported in the product apply.
Next steps
Add contacts under Alert contacts, assign them to monitors, and send a test notification.
What you can verify with SitePuls here
- Email contacts receive incident notifications based on the monitors they are attached to.
- The reporting area can email CSV uptime/SLA exports for a monitor to a recipient when you use that action in the UI.
Where incident alerts can go
- Email addresses saved as alert contacts receive messages when incidents open or resolve (according to your notification settings).
- Telegram notifications via the SitePuls bot after you link a chat to an alert contact (including the bot /start flow for pending contacts).
- HTTPS webhooks that receive JSON with event type, monitor identifiers, status, timestamp, optional incident id, and a short message for generic integrations.
- Slack-compatible incoming-webhook formatting: alert contacts can use a dedicated mode so payloads match Slack-style incoming webhook expectations.
Illustrative sample — field names match the product; values are placeholders.
What email downtime alerts look like
- Subject uses `[SitePuls]` plus the monitor URL, same pattern as the live email channel.
- Body is plain text from the scanner/incident message—not a separate marketing template.
- Routing uses the same Alert contact record you attach to the monitor (email, Telegram, or webhook).
FAQ
Can I use group mailing lists?
Yes if the address can receive external mail and you add it as a contact.
HTML or plain text?
Follow what the product sends today—focus on actionable subject lines and links back to incidents.
Per-monitor email?
Assign different contacts per monitor for routing.
Confirm email vs alert email?
Account confirmation uses separate flows—alert contacts are for operational notifications.
Rate limits?
Expect bursts during widespread failures; design paging accordingly.
GDPR and logging?
See the privacy policy for data handling; operational mail may contain monitor metadata.
Mute nights?
Use smart alerts or escalation policies where the product supports them on your plan.
Where do I add email contacts?
Alert contacts in the SitePuls app after sign-in.