Notification Channels

Notification channels let you push the right information to the right place at the right time. Configure per-workspace rules to determine which events trigger a notification and where it goes.

Notification triggers

You can configure notifications for any combination of:

• New incident created — at a specific severity level or above
• Incident severity escalated — e.g. a medium escalated to critical
• SLA at risk — when an incident is approaching its SLA deadline
• SLA breached — when an incident has missed its SLA
• Incident closed — optionally with a summary
• Client report ready — when an auto-drafted report is ready for review

Each trigger can be routed to one or more channels.

---

Slack

Prerequisites: A Slack workspace where you have permission to add apps

Setup

1. In Seliq: Settings → Notifications → Add channel → Slack
2. Click Connect to Slack — you’ll be redirected to Slack’s OAuth authorisation
3. Select the workspace and click Allow
4. Back in Seliq, choose the default channel for notifications (you can override per trigger)
5. Configure which triggers send to which channels

Notification format

Seliq Slack notifications include:

• Severity badge (coloured)
• Incident title and client name
• AI summary (first 2 sentences)
• Direct link to the incident in Seliq

---

Email

Seliq can send email notifications directly, either using the Seliq shared sending domain or your own domain.

Using the Seliq sending domain

No configuration needed. Notifications are sent from alerts@notifications.seliq.io. Add this address to your allowlist to prevent delivery to spam.

Using your own domain

See White-label Reports for instructions on configuring a custom sending domain via DNS.

Notification configuration

1. In Seliq: Settings → Notifications → Add channel → Email
2. Enter one or more recipient email addresses (comma-separated)
3. Choose the triggers and minimum severity threshold
4. Optionally set a daily digest mode to batch low-severity notifications

---

PagerDuty

Prerequisites: A PagerDuty account with permission to create a new service or integration

Setup

1. In PagerDuty, create a new service or open an existing one
2. Under Integrations, add a new integration and select Events API v2
3. Copy the Integration key (routing key)
4. In Seliq: Settings → Notifications → Add channel → PagerDuty
5. Paste the integration key
6. Set the severity mapping: Seliq critical → PagerDuty critical, high → error, medium → warning

On-call routing

Use PagerDuty’s escalation policies and on-call schedules to route Seliq critical alerts to the right analyst, even outside business hours. Seliq sends standard PagerDuty Events API v2 payloads, which means all PagerDuty features — deduplication, suppression, escalation — work as normal.

Coming soon

Microsoft Teams and Opsgenie integrations are on the near-term roadmap.