Skip to content
Messaging cost control

A $100/mo wall between you and a runaway drip sequence.

Drip sequences and bulk blasts are powerful — and one mis-configured trigger can fire thousands of sends in an afternoon. The Messaging Spend Cap is the per-shop ceiling that stops that from becoming a surprise bill.

No credit card
Cancel anytime
/app/settings/payments
SMS + email usage bars, overage-vs-cap status, raise-the-cap control, and a BYOC callout — all inside the same Settings → Payments page as the processing-fee settings.

The quick version

Texting spend cap: A monthly limit so extra texting never surprises you.

  • $100/mo per-shop default cap on OVERAGE dollars, once you're past your tier's included SMS/email allowance
  • Live usage bars + overage status in Settings → Payments
  • In-page color warning at 75% of the cap, red at 100% — no push/email/Slack alert today, you see it when you open the page
Which plan includes this? See pricingTry it in the Test Drive

Sends within your plan tier's included SMS/email allowance are free and don't touch the cap at all; once a shop goes over that allowance, every additional send — including automated reminders, not just drips and blasts — draws against a single monthly overage bucket, confirmed in code ("Every send path — drips, reminders, review requests, blasts, automation ticks, etc. — passes through this central gate"). Default cap is $100/mo of overage per shop. Hit it, new sends pause until you raise the cap in Settings → Payments or the month resets. For shops sending genuinely high volume, BYOC mode lets you bring your own Twilio + Resend credentials and skip the cap entirely — pay your carrier directly.

Everything it does

The complete list. The plan tag above shows which plans include it.

  • $100/mo per-shop default cap on OVERAGE dollars, once you're past your tier's included SMS/email allowance
  • Live usage bars + overage status in Settings → Payments
  • In-page color warning at 75% of the cap, red at 100% — no push/email/Slack alert today, you see it when you open the page
  • Applies to every send once you're over allowance, including automated reminders — not just drips and blasts
  • Self-service raise up to $1,000/mo overage; above that needs a manual admin override
  • BYOC escape hatch — bring your own Twilio + Resend, skip the cap, pay carriers direct
  • Audit log entry every time the cap is raised or lowered

Who it's for

Built specifically for…

  • Every shop running drips or bulk blasts (default-on insurance)
  • Multi-location owners who can't personally audit each shop's messaging config weekly
  • High-volume shops who want to opt into BYOC and skip the cap entirely

What it replaces

The old way…

  • The 4am Twilio bill that shows $480 because someone enrolled the entire customer base in a 7-step drip
  • Manual nightly spend audits the owner kept forgetting to do
  • 'I'll just turn off the campaign if it gets too expensive' — too late, you already paid

Setting it up

  1. 1

    1. Default cap is on

    Every new shop ships with a $100/mo overage cap pre-set. Sends inside your tier's included SMS/email allowance are free; once you're over that allowance, every additional send — automated reminders included — draws against the overage bucket.

  2. 2

    2. Status shows in Settings → Payments

    Usage bars turn amber near 75% of the cap and red at 100%. There's no push, email, or Slack alert today — you see the status when you open the page.

  3. 3

    3. Cap hits, new sends pause

    Once overage hits the cap, further sends — including automated reminders — pause until you raise the cap or the calendar month rolls over. Volume Packs (extra SMS/email allowance on top of your plan) are coming soon; until then, raising the cap is how you keep sending.

What this looks like in a shop

Illustrative scenario: a new tech at Sample Shop LLC accidentally wired a welcome drip to fire on every customer record instead of just new ones, well past the shop's included SMS allowance for the month. At roughly 1.5¢/segment overage, the queued batch would have added real cost on top of an already-elevated running spend. The cap stopped new sends once the overage total hit $100 for the month. Mike opened Settings → Payments, saw the cap maxed out with a red status, raised it to $200 for the rest of the month, and fixed the drip's trigger.

Good to know

Does the cap block transactional comms too?
Yes, once you're over your included allowance — appointment reminders, review requests, and other automated sends go through the same gate as drips and blasts. There's no separate transactional bypass; the code's own comment on the gate says "every send path... passes through this central gate."
Can I raise or lower the cap?
Yes — Settings → Payments. Every change is audit-logged. You can self-raise up to $1,000/mo of overage; above that needs a manual admin override.
What's BYOC and how does it skip the cap?
Bring-Your-Own-Carrier. Plug in your own Twilio + Resend credentials in Settings → Integrations and SalesThumb routes your shop's sends through your account. SalesThumb's cap doesn't apply because we're not the one billing you.
What if I have multiple shops?
Each shop has its own cap and its own Settings → Payments page. There isn't an HQ-facing rollup page showing every shop's cap utilization in one place today.

Works with your stack

Tw

Twilio

Per-segment overage cost computed at read time against the cap

Re

Resend

Only if you connect your own Resend account (BYOC), which skips the cap; platform email is metered at a flat per-email rate against the cap

Try spend cap — no credit card.

Pick Basic, Starter, Growth or Pro on the pricing page and it's free for 30 days, no credit card. Some features need a higher plan; the pricing page shows which. Import your old data and be running by tomorrow.