SoftStop

Open source · Next send

Don’t drop the send.
Get the next one.

check returns send now, send at T, or send on another type or channel. Same volume intent — no mute without a slot. You still fire; SoftStop does not enqueue.

Quick Start

install
# Deny always includes sendAfter or a cheaper type. You still send.
$ npm i softstop

JS/TS client from npm. Point it at a self-hosted SoftStop API (pnpm dev → http://localhost:3000). Alternates: curl -fsSL https://softstop.vercel.app/install.sh | bash or npm i https://softstop.vercel.app/softstop.tgz

Self-host for production. softstop.vercel.app is the live demo and SDK CDN — not a production SoftStop host.

Growth owns volume. SoftStop names the next send: sendAfter or suggestedFallback. Call check/record at send time — pull, not a push.

usage
import { SoftStop } from 'softstop'
const ss = new SoftStop({ url: 'http://localhost:3000' })
const d = await ss.check({ userId: 'u1', actionType: 'urgency' })
if (!d.allowed) {
  // d.reason, d.explanation — optional d.suggestedActionType ("reminder" for urgency/interruption)
  await ss.record({
    decisionId: d.decisionId,
    userId: 'u1',
    actionType: 'urgency',
    outcome: 'blocked',
    blockReason: d.reason
  })
  return
}

How it works

Docs →

Ask before you fire. Always leave a next send.

Your stack still writes the copy and fires the message. SoftStop answers may I send this, or what instead? allowed: true = send now. Deny always includes sendAfter and suggestedFallback (cheaper type now, or another surface). SoftStop does not enqueue.

Email
check →
SMS
check →
Push
check →
Popup
check →
Ads
check →
Agent
check →
email · urgencyallow
sms · reminderallow
push · urgencyblock
popup · discountblock
Allow
record landed
Block
record blocked
01
Any system

Email, SMS, push, modal, ads, agent — each about to send.

02
check()

Ask SoftStop with userId, actionType, surface.

03
Shared journal

Decision uses the same per-customer history — not a silo per tool.

04
record()

Always write the outcome — including wait — so the next send isn’t blind.

Send nowallowed: true

You may send this. You still originate it. Journal the landing.

Send at T / theredeny + next

sendAfter to reschedule, or suggestedFallback for a cheaper type / next surface. Still record.

{
  "allowed": false,
  "reason": "pressure_exceeded",
  "retryAfterMs": 9000000,
  "sendAfter": "2026-09-04T14:30:00.000Z",
  "suggestedFallback": {
    "strategy": "downgrade",
    "actionType": "reminder",
    "surface": "push"
  }
}

Action types

Four kinds of send

Same path — kind → check → send now, send at T, or send there.

urgency
time pressure
discount
price / promo
interruption
modal / popup
reminder
soft nudge
Send now
good minute
Wait
wrong minute

Live example

7 days, many channels, one next send

Same stacked campaign. SoftStop doesn’t write the message. ON means a deny is a wait until / try reminder — not a cut in volume.

OFF → every touch LANDED. ON → excess shows WAIT with a next slot, not a mute.

Pressure
Relaxed 0
😵

Death by a Thousand Touches

This is what multi-channel automation looks like without coordination.

Illustrative demo outcomes — not measured LTV or brand metrics

Without SoftStop
User churned
Marked as spam
$0 lifetime value
Damaged brand reputation
With SoftStop
User retained
Healthy engagement
$247 lifetime value
Positive brand sentiment
0
Touches
0
Blocked
0
Peak
8
Channels
Try again with SoftStop ON

Why this, not less mail

GitHub →

We don’t cut the campaign. We reschedule or reroute.

Growth wants volume. A veto with no clock is a tax on that job. Every deny now names the next send: sendAfter or a cheaper type / next surface. You still fire. SoftStop still does not originate messages.

Without SoftStop · pile-on, no next slot

Growth
urgency blast
CRM
discount drip
Support
reminder ping
Ads
retarget
Product
interruption
Agents
outreach
cust_1042
cust_881
cust_2207
cust_559
cust_3301
cust_774
cust_4156

With SoftStop · next send named

Growth
urgency blast
CRM
discount drip
Support
reminder ping
Ads
retarget
Product
interruption
Agents
outreach
cust_1042
cust_881
cust_2207
cust_559
cust_3301
cust_774
cust_4156

Next send on every deny

sendAfter plus a cheaper type or next surface. Don’t mute without a slot.

Your stack still fires

Authorize-only. SoftStop does not enqueue or wake your ESP. You honor the next send.

Volume is the KPI

Measure sends executed after wait or reroute — not blocked count.