Sendblue pricing, explained

What Sendblue publishes today

Sendblue’s pricing page lists three tiers. This guide uses only the figures on that page, retrieved on August 27, 2026. Pricing pages change; confirm the current terms directly before you commit.

The important detail is not the dollar amount on each tier. It is the outbound restriction that separates them.

• Free Sandbox — $0, shared number, full API access, limited to 10 verified contacts, inbound-first
• AI Agent — $100/month per dedicated line, up to 1,000 inbound contacts per day, media and typing reactions, webhooks and callbacks, priority support
• Enterprise — custom pricing, everything in AI Agent plus full outbound messaging, multiple dedicated lines, SOC 2 and HIPAA, dedicated account manager

The sandbox is for testing, not for reaching people

The free tier gives you real API access against a shared number, capped at ten verified contacts, and it is inbound-first — the contact texts you before you can text them. That is enough to write an integration, exercise webhooks, and see the message shape.

It is not enough to evaluate a sales or support workflow, because the constraint that matters in production — who may start a conversation — is exactly the constraint the sandbox holds fixed. Plan to test the integration for free and to test the workflow on a paid tier.

What $100 per month actually buys

The AI Agent plan is a dedicated line at $100 per month with an inbound allowance of up to 1,000 inbound contacts per day, media and typing reactions, and webhooks and callbacks. For a product that answers customers who contact it — a support line, an AI agent, a reply-driven assistant — that is a coherent unit of purchase.

Read the tier name literally. It is built around a conversation the customer starts. If your business case is proactive outreach, the published $100 is not the number your quote will be based on.

Where Enterprise begins

Sendblue’s page places full outbound messaging, multiple dedicated lines, SOC 2 and HIPAA, and a dedicated account manager in the Enterprise tier, priced on request. Outbound sales teams, multi-line agencies, and regulated buyers therefore do not have a published price at all.

This is not unusual in the category — Linq publishes no production figure either — but it changes how you should read comparison tables. A table that puts Sendblue at $100 against a competitor’s outbound line price is comparing two different products.

• Confirm in writing which tier permits business-initiated messages
• Confirm the per-line price at the number of lines you actually need
• Confirm whether SOC 2 or HIPAA coverage is contractual or aspirational
• Confirm what a dedicated account manager is committed to in the SLA

What Sendblue says is not billed

The page states that there are no per-message fees, no A2P registration charges, no carrier surcharges, and no SMS fallback fees, with volume discounts available at ten or more lines and on annual billing.

That is a genuinely simpler unit than a carrier-mediated SMS program, where 10DLC registration, campaign vetting, and per-segment charges all show up separately. When comparing against an SMS budget, remember you are removing several line items, not only changing one.

The daily contact limit is the real capacity number

A flat monthly price with a daily contact cap behaves like metered pricing once you approach the cap. At 1,000 inbound contacts per day per line, capacity planning is a division problem: your peak day divided by the cap gives the number of lines, and the number of lines gives the bill.

Model the peak, not the mean. A support line that averages 300 conversations a day and spikes to 1,400 after an outage needs the spike modeled, or the incident becomes the moment the channel stops working.

Published prices across the category

For context, here is what other providers published as of late August 2026. These are headline figures from each vendor’s own pricing page and are not normalized — the units differ, and several are not comparable without reading what each tier permits.

Use this as a map of the pricing models in the market, then build a real comparison from the workflow you intend to run.

• Miss Blue — $39/month shared testing number; $99/month per dedicated number with unlimited commercial usage, contacts, team access, Message Center, and API access
• Sendblue — free sandbox; $100/month per line inbound-first; outbound on Enterprise quote
• Blooio — $39/month shared starter; $109/month inbound; $289/month Commercial Dedicated
• Project Blue — $300/month plus $500 setup, or $166.50/month billed annually with setup waived
• Blue Reacher — $249/month per line plus $449 one-time activation, waived on annual
• Tuco AI — from $149/month plus a $335 one-time setup fee
• Claw Messenger — from $5/month on a metered message allowance
• Linq Blue — no published production figure; Enterprise quote

Normalize before you compare

The tiers above are priced in at least four different units: per shared number, per dedicated line, per metered message, and per custom agreement. A straight column of dollar signs will rank them wrongly.

Build one scenario and price every vendor against it: the number of lines, whether conversations are inbound or outbound, peak daily conversations, teammates who need inbox access, attachments, retained history, and the support response you need when delivery degrades.

• Lines required at peak, not at launch
• Who is permitted to start the conversation
• Daily and monthly conversation caps per line
• Seats in a shared inbox, if one is included at all
• One-time setup, activation, and area-code fees
• Contract length and what happens to the number at cancellation

Count what the price does not include

A messaging API can look complete after one successful send while leaving retries, idempotency, event verification, delivery reconciliation, media storage, permissions, and a human inbox to the buyer. Those become engineering time, and engineering time is the most expensive line in most of these comparisons.

Before signing, run the same five tests against every candidate: an inbound reply, a duplicate webhook delivery, a failed destination, a teammate taking over a live conversation, and a full data export. Whatever fails belongs in the cost model.

Questions worth asking before you buy

Get answers in writing, on the tier you will actually be on, at the volume you actually expect. Verbal assurances about outbound rights are the single most common source of surprise in this category.

Ask the same questions of every vendor, including Miss Blue. A provider that answers them precisely is telling you something about how it will behave during an incident.

• Which tier permits business-initiated outbound, in writing?
• What are the per-line daily and monthly limits?
• What happens when a limit is reached — throttle, queue, or hard stop?
• Are inbound messages, failures, and retries billable?
• Is a shared team inbox included, or is it API-only?
• Who owns the number if we leave, and can it be ported?
• What is the contractual support response when delivery degrades?

Where Miss Blue sits

Miss Blue publishes $39 per month for a shared testing number and $99 per month per dedicated number, with unlimited commercial usage, contacts, team access, the Message Center, and API access included on the dedicated plan. Optional managed Conversational AI is $100 per month plus a one-time $250 setup fee; a specific area-code request is a one-time $205 fee where inventory permits. Connecting your own AI agent through the standard API is included.

The displayed $39 and $99 figures are current 50%-off sale rates against regular prices of $78 and $198, locked in while the plan remains active. Enterprise pricing is custom. Compare that against the tier you would actually be sold elsewhere, not against a headline that belongs to a different workflow.