How long would a silent stop on your email flow hide before your team noticed?

Your email setup

Defaults reflect a typical mid-market operator. Override any field you have a better number for.

Total company revenue from your last financial year. A rough figure is fine, we only use it to suggest a default daily-send number below, which you can override directly. Current value: $50,000,000.

Sets the community-median detection time we anchor the comparison column against.

The flow we model is the one whose silent stop would hurt most. Sets the default daily volume and per-send revenue anchor.

Default tracks revenue + ESP.

If you do not have the exact figure, leave the default. You can verify it later against your ESP's last-30-day flow report.

Each option maps to a typical time-to-detect. The "what would catch this today" paragraph below explains the catch signal for your routine.

Ready to see how long it would hide?

Press calculate to see how many days a silent stop on your top flow would hide before anyone noticed, and how that compares to the community median for your sending platform.

Your detection gap

If your top flow stopped sending today

Set the inputs above to see your detection gap.

That is the top line. The full breakdown shows how your routine compares to the Klaviyo community median, how much of the lost revenue you can claw back versus what is gone for good, and what would actually catch this in your stack today. We email it to you along with a 7-page PDF of the failure patterns operators report most often on your sending platform.

We use your email to send the PDF and the occasional Telltide brief. One-click unsubscribe in every email.

Your setup Community median
Time to detect a silent stop — —
Sends missed in that window — —
Recoverable through backfill — —
Unrecoverable revenue (lower / upper) — —
Daily sends from this flow
—
Anchored from revenue + ESP, overridable.
Time to detect (your setup)
—
Mapped from your discovery method.
Sends missed before catch
—
daily sends x time to detect
Revenue at stake
—
sends missed x revenue per send (flow anchored)
Unrecoverable (lower band)
—
revenue at stake x 30% unrecovered (best-case backfill)
Unrecoverable (upper band)
—
revenue at stake x 80% unrecovered (limited backfill)

The gap is real. The next step is closing it.

The fastest path in is one high-value flow on the free tier. You name the flow, point Telltide at the trigger, and email alerts start landing the moment a window goes silent. Day one becomes the catch day, not the day the support queue tells you something went wrong.

When you move to Starter, the Detection Guarantee covers your first 90 days. If we miss a silent send failure on a monitored flow inside that window, we credit up to three months of the affected tier.

Try free

Common questions

A CRM-triggered send that should have left the ESP but did not, with no signal in the dashboard until revenue drops or a customer complains. Examples include a flow that drops after a trigger metric is renamed, a campaign stuck on "Ready and waiting", or a Smart Sending guardrail skipping a flow email. The PDF lists the full pattern library.
An aggregate of operator interviews, community-forum incident postmortems, and public retros conducted across Klaviyo, Iterable, Braze, HubSpot, Customer.io, Salesforce Marketing Cloud, and Marketo programmes. The number is conservative, since survivor bias means severe incidents are the ones that get written up. Your real-world catch time is likely a touch longer than your selected discovery method suggests.
Annual exposure compounds three assumptions on top of each other (incident rate, detection window, recovery rate) and gives you a number with the working hidden. Per-event is one assumption per cell, all visible, all overridable. Multiply by your honest incident rate to get the annual figure you can actually defend.
Deliverability degradation, inbox placement loss, the cost of a wrong-segment send, and the reputational cost of a duplicate. The model handles the silent-stop pattern only, which is the one most teams have no instrumentation for today.
So we can send the PDF to your inbox, where you can forward it to a colleague or attach it to a finance conversation. We follow up with the occasional Telltide brief and nothing else. One-click unsubscribe in every email, and we do not sell or share the list.
Yes, by watching the live send stream from outside your ESP. If a flow that fired daily for six months stops sending today, you get a wallet-card alert within minutes, not at month-end review. The free tier covers one flow. Paid tiers start at $49 a month and add the wallet card.
Override it. The default is anchored from annual revenue, ESP, and flow type, but real volume varies by a factor of two or three across programmes of the same size. Type the number you see in your ESP's last-30-day report and the rest of the calculation re-runs on your inputs.