ServiceCap · Waitlist

Know your WhatsApp service bill before Oct 1 — not after Meta starts charging per message

Import Pricing Analytics or webhook CSV (or connect WABA). Forecast your Oct+ monthly service bill against the Oct-1 rate card, list multi-bubble waste and savings if you merge replies, track the 1,000 free/month burn per number, and get a Sep-30 payment checklist plus questions to ask your BSP for written pass-through rates. Not an inbox or sender — a cost-readiness layer before free replies end.

Join Waitlist See how the service-cost audit works

Market-validation page · Free waitlist · No fake user counts

Problem

Free replies end Oct 1

Since ~2024-11 free-form service replies (and in-window utility from 2025-07) were nearly free — teams built multi-bubble, chatty bots. From 2026-10-01 Meta charges every delivered service message at each market’s utility/authentication rates; 1,000 free per number/month (no rollover); no service volume discount. No payment method by 2026-09-30 → delivery may stop Oct 1. BSPs often add 15–35% markup. Static calculators educate; they don’t give real-usage readiness.

Before

Free-era multi-bubble / chatty confirms; Oct bill unknown
Static calculator / Excel / wait for invoice
Sep-30 payment and BSP markup are guesses

After

Real usage × rate card → Oct+ monthly bill forecast
Waste list + merge savings + free-tier exhaustion date
Payment checklist + written pass-through question list

Join Waitlist

Solution

What ServiceCap does

A cost-readiness layer for Cloud API / BSP support and transactional flows: import → forecast → multi-bubble audit → free-tier burn → Sep-30 / BSP checklist — not another static calculator or inbox.

WHO

DTC / ecommerce ops, support leads, or WhatsApp agencies running support, COD confirms, and order-status flows via WhatsApp Cloud API (BSP such as 360dialog / Twilio or direct), with outbound service volume clearly above 1,000 messages per business phone number per month.

PROBLEM

Free-era multi-bubble bots become billable on Oct 1 2026. 1,000 free/number/month, no rollover, no service volume discount. Sep-30 payment gap risks stop-delivery. BSP markups 15–35%. Static calculators can’t show your waste or exhaustion date.

SOLUTION

Import Pricing Analytics / webhook CSV or connect WABA → Oct-1 rate card bill forecast + merge-savings → free-tier burn & exhaustion date → Sep-30 payment checklist + BSP written pass-through questions.

RESULT

Know your WhatsApp service bill and savings levers before Oct 1 2026 — not after Meta charges per message or the first invoice lands.

Features

Marketing points from the product hypothesis — for demand validation, not a formal spec promise.

📥

Usage import → Oct+ bill forecast

Accept Pricing Analytics / webhook CSV or connect WABA; forecast monthly delivered service bill against Oct-1 utility/auth rate cards (minus 1,000 free per number).

💬

Multi-bubble waste audit

Flag mergeable confirm chains / empty info bubbles; estimate savings if you merge or delete — aligned with public industry signals that multi-bubble is a top lever.

🔥

1,000 free-tier burn dashboard

Per business phone number: free used, remaining, and estimated exhaustion date (no rollover semantics).

✅

Sep-30 payment + BSP markup checklist

Billing Hub payment-method deadline checklist; questions to ask your BSP for written pass-through vs 15–35% markup.

📄

Readiness report export

MVP: import + forecast + audit report (PDF/CSV). Explicitly not message sending, inbox, or becoming a BSP.

How it works

A three-step loop matching the waitlist-stage product hypothesis.

1
Import usage or connect WABA
Pricing Analytics / webhook CSV (or WABA) — align delivered service / in-window utility.
2
Forecast bill & audit waste
Oct-1 rate card × usage; multi-bubble waste + merge savings; 1,000 free/number burn and exhaustion date.
3
Checklist & report
Sep-30 payment checklist + BSP pass-through questions; export readiness report — not an inbox or sender.

Join Waitlist

Use cases

Who it’s for

If these situations sound familiar, join the waitlist to help us validate.

Support / COD / order-status bots with multi-bubble confirms

See how much merging saves — not just fill a static calculator with assumed volume.

Outbound service ≫ 1,000 / number / month

Need free-tier exhaustion date and Oct+ bill forecast to align finance / leadership.

High-rate markets (e.g. Germany $0.055/msg example)

10k msgs − 1k free → ~$495/mo scale; need attributable forecast and savings list.

On 360dialog / Twilio / other BSPs

Clarify pass-through vs markup before the Oct invoice shock.

Payment method not linked before Sep 30

Need a checklist to avoid Oct 1 stop-delivery — risk dwarfs a $19–$49/mo tool.

Public signals

Public signals from the industry

Public reporting and industry discussion only — not customer testimonials or invented metrics.

FAQ

How is ServiceCap different from Peach-like static pricing calculators?

Those use assumed volumes. We connect real usage for forecast, waste audit, and free-tier exhaustion.

How is it different from Respond.io / Conferbot / Landbot?

Those are inbox / bot platforms. We are an independent cost-readiness layer — not an inbox.

Do you send WhatsApp messages or act as a BSP?

No. MVP is import + forecast + audit report — not sending, inbox, or becoming a BSP.

What is the 1,000 free tier?

Meta: 1,000 free service messages per business phone number per month; unused do not roll over; no service volume discount (see Meta pricing docs).

What if I don’t add a payment method by Sep 30?

Per Meta non-template docs, service message delivery may stop when charging starts Oct 1.

What’s in MVP scope?

CSV / Analytics import (+ optional WABA) + forecast + audit report. Sending, inbox, and BSP are out.

When is early access?

Waitlist invites go out in batches by email. No fake launch date.

What’s the expected price?

Hypothesis band $19–$49/mo; final pricing arrives with launch email.

Waitlist

Join the waitlist

Leave your email for ServiceCap early access and launch notes. We will not invent a ship date.