Skip to main content
GreenSlope

Product · Incident loop

The incident workflow,
closed — not just observed.

Most observability tools stop at detection. Greenslope is Auto-SRE: alert, triage, suggest rollback, capture what you did, and close the loop. The Slack integration is the primary surface — no context-switch, no separate console to learn.

Serves this job

"When an alert fires, I want to ack / snooze / resolve without leaving Slack." (JTBD 3) · "When Greenslope suspects a bad release, I want a prominent rollback suggestion with a deep-link." (JTBD 6) · "When an alert is acked / snoozed / dismissed, I want Greenslope to learn." (JTBD 11) · "When I come on-call, I want a digest of the last 12 hours." (JTBD 12)

§ 01How it works

Alert, decide, move on — without leaving Slack.

Install the Slack App once. Alerts arrive in the channel of your choice with interactive buttons. Everything you do flows back into the triage record.

Interactive Slack alerts

Each alert message includes Ack, Snooze, and Resolve buttons. Clicks are attributed to the Slack user; decisions and timestamps are recorded on the incident.

Multi-channel delivery

Slack is the primary surface. Alerts can also deliver via generic webhook (HMAC-signed), email, SMS, and voice via Twilio. Up to two delivery channels per alert rule at Solo / Starter.

Rollback suggestion in-line

If a release is implicated, the alert includes a rollback suggestion with a deep-link to the Vercel rollback dialog. One human click away from a revert; no autonomous action.

Self-tuning thresholds

Repeated snoozes teach us the alert is too noisy. Repeated acks teach us it's useful. Greenslope tunes the thresholds it proposed for you without asking.

On-call digest

Coming on-call? Greenslope posts a 12-hour digest to your channel: open incidents, recently-resolved ones, last 10 deploys, and any endpoint sitting on the wrong side of its SLO.

Last-N incidents context

Every alert surfaces the last N incidents on the same endpoint with actions taken and linked postmortems — so you aren't debugging the same issue from scratch.

§ 02Delivery channels

What's wired up today.

What ships today

  • Slack App with interactive Ack / Snooze / Resolve buttons.
  • Generic outbound webhook with HMAC signing (escape hatch for anything we don't natively integrate).
  • Email alerts to on-call recipients.
  • Twilio SMS alerts — included allowance: 50/month on Solo, 300/month on Starter.
  • Twilio voice alerts — included: 20 minutes/month on Solo, 120 on Starter. Opt-in per rule.
  • PagerDuty as a send-events-in target via webhook for customers already on it.

Out of scope (or V2+)

  • On-call rotation scheduling — V2+ at Team tier. V1 Twilio is per-recipient on the alert rule.
  • Mobile push notifications — V2+, requires a native mobile app.
  • Microsoft Teams alert delivery — V2+ on design-partner demand.
  • Per-service team routing — V2+ at Team tier.
  • Per-incident chat within the product — V2+.
  • Over-quota SMS / voice add-ons — V1 is a conversion signal to upgrade, not metered overage.

Get started

See what your last 10 deploys really did.

Point GreenSlope at one service. Five minutes to first insight. No credit card, no sales call. If you don't like it after 30 days, we'll help you export everything.