Sendblue pricing, explained

How much does Sendblue cost?

Sendblue lists a free sandbox, a $100 monthly AI Agent line, and an Enterprise quote for full outbound. Choose the tier by who starts the conversation before comparing the price. The table summarizes its official pricing page checked September 13, 2026.

Can you test Sendblue webhooks for free?

Sendblue’s public pages disagree: the pricing table excludes webhooks and callbacks from the free sandbox, while the homepage FAQ says event support comes with every plan. We have not verified account-level enforcement. Confirm sandbox webhook access with Sendblue before upgrading or depending on it for a reply integration.

Split your acceptance checklist into request validation, live channel behavior, and event handling. A mock event can test your parser; only an actual provider delivery verifies signature handling, retry behavior, and the way your endpoint acknowledges events. Record which tests used fixtures and which used actual provider events.

• Sendblue pricing table
• Sendblue homepage FAQ

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.

Price the workflow and its peak day

Count unique contacts, messages, and lines separately. Ten messages in one conversation do not necessarily consume ten contact allowances. Ask when the daily window resets, what happens at the limit, and whether the allowance is pooled.

A line that averages 300 contacts and peaks at 1,400 needs a documented overflow plan. Dividing the peak by a published cap is a planning estimate, not proof that another line can accept the traffic: customers may continue texting the original number, and multi-line terms may require Enterprise.

Compare a matching production plan

An inbound assistant, a shared test number, and a business-initiated sales line solve different jobs. Ask each finalist to price the same contact volume, sender count, outbound requirement, staff access, and support expectation.

Keep the detailed provider shortlist in the alternatives guide so this pricing page can answer the cost question without mixing incompatible entry tiers.

• Compare Sendblue alternatives and plan a migration
• Compare iMessage API operating models
• See current Miss Blue plans and optional charges
• Compare Sendblue with Twilio by channel and complete cost

One line, three lines, and an outbound team

These are budget examples, not vendor quotes. One eligible inbound AI Agent line has a $100 monthly base before any applicable taxes or extra services. For three such lines, 3 × $100 = $300 is arithmetic only: Sendblue places multiple dedicated lines under Enterprise, so confirm that configuration and its price with sales.

A team initiating conversations with new leads needs an outbound quote even if it only wants one number. Enter an unknown price in your budget until that quote arrives; using $100 would give a precise-looking answer for the wrong entitlement.

For a fair comparison, calculate monthly service cost plus setup amortized over your expected term, optional integrations, and staff time. Example: a hypothetical $300 setup spread over twelve months contributes $25/month. This is a budgeting method, not a claim that Sendblue charges that fee.

Normalize before you compare

Across the category, providers use shared numbers, dedicated lines, metered messages, and custom agreements as commercial units. A straight column of dollar signs can rank unlike plans together.

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.