EscalatePricing

Coverage Report

The Coverage Report is Escalate's at-a-glance view of every deal it's watching, every trigger rule in force, and every alert it's fired. Two surfaces:

  1. Monthly digest DM — auto-delivered to the founder on the 1st of each month. No action required to receive it; it just shows up.
  2. On-demand console — generated via /escalate coverage. Returns a single-use magic link (15-minute expiry) to a web page with the same numbers plus drill-downs.

Insurance vocabulary

The Coverage Report borrows insurance terminology because the analogy is exact: Escalate provides coverage against a class of silent failures (cross-functional stall), and the metrics that matter are the same ones an insurance carrier reports to a policyholder.

Covered

A covered deal is one where a deal channel exists and Escalate is actively watching sub-threads. Counted weekly + monthly. A deal becomes covered the moment its qualifying trigger fires and the channel auto-creates.

Claim

A claim is an alert that fired — Escalate detected a stalled sub-thread and DM'd the founder. Counted by deal + by role + by month. The claim record stays in the audit chain whether you acknowledged it, snoozed it, or pinged the channel.

In-force

An in-force rule is a trigger configuration that's currently matching incoming CRM updates. If you've set qualifying stages but turned off the workspace (e.g., via cancellation grace period), the rules are no longer in-force. Run /escalate config trigger to view current in-force rules.

Suspended

A suspended rule was in-force at some point but is now paused. Reasons: workspace cancellation grace period, founder explicitly suspended the rule, or the CRM connection was revoked. Suspended rules return to in-force when the underlying issue clears.

Alerts

A weekly count of claims that fired. The "alerts last 7 days" line on /escalate stats is the same number. High alert volume usually means thresholds are too tight (or your team has a real workflow problem); see Thresholds for tuning guidance.

Stalls

A stall is a sub-thread that's currently past its silence threshold but where the founder hasn't yet taken an alert action. Distinct from claims: a claim is the alert-fired event; a stall is the current state. Stalls roll into claims the moment the alert posts, then back out once you act on the alert.

What the monthly digest DM contains

Delivered as a Slack DM to the founder on the 1st of each month. The digest is read-only — no action buttons.

Sections:

  1. Coverage summary — count of covered deals at month-end + month- over-month delta.
  2. Claims — total alerts fired for the month, broken out by role (Legal / Security / Compliance / Other).
  3. In-force rules — the qualifying stages + minimum amount + role mappings in effect as of month-end.
  4. Top stalls — up to 5 deals whose sub-threads were stalled longest, with the role + business-day count.
  5. Trailing precision — share of alerts in the last 30 days you marked as legitimate vs. dismissed. Below 60% triggers a fine- tune or threshold-loosening conversation.

What the on-demand console contains

Generated via /escalate coverage. The magic link expires in 15 minutes; click it within that window. The console shows:

  • The same Coverage / Claims / In-force / Suspended counters as the digest.
  • A deal table with one row per covered deal — last activity, current stall state, role assignments.
  • A claim timeline with one row per alert — when it fired, what role, what action you took, the elapsed time to action.
  • A rule inspector showing the current trigger configuration + any rules that flipped state during the month.

Reading the trailing-precision number

Trailing precision = (alerts you marked legitimate) / (total alerts in the rolling 30-day window). The "legitimate" signal comes from the alert action you took:

  • Ping / Take it → legitimate (you took action).
  • Acknowledge → legitimate (you saw it; no action needed but alert wasn't noise).
  • Snooze 48 BH → legitimate (it's a real ask; you just need time).
  • Dismissed (alert-followup "dismiss" button) → NOT legitimate (you marked it noise).

Target: ≥80% trailing. Below 60% triggers a classifier fine-tune or threshold change. See the pricing page for the framing.

Common questions

How do I get an export of the data?

Run /escalate audit-export workspace for the full audit chain. See Slash commands.

Today, no — the console is gated by single-use magic link to avoid session-cookie sprawl. If you want a more durable surface, ping the founder.

What's the difference between a "claim" and an "alert"?

Identical for V1 — same underlying event. The two words exist so the report reads in the insurance dialect throughout.

Next steps

  • Generate the console now: /escalate coverage from any Slack workspace with Escalate installed.
  • Tune the noise floor: Thresholds.
  • Want the lifecycle narrative? What Escalate does.