A JOURNAL OF MESSAGING INFRASTRUCTURENO. 01 / 2026
Protocol Review

Sendblue

Sendblue: production scope before SDK choice.

The most material purchasing boundary is inbound versus full outbound.

Browse practical guides →
An inbound-first published plan cannot price a proactive application.

Documented commercial boundary

Sendblue’s pricing page lists the $100-per-line monthly AI Agent plan as inbound-first. Full outbound messaging is an Enterprise purchase with custom pricing. An evaluator should specify whether reminders and follow-ups initiate new conversations, because that requirement can change the plan before any SDK decision matters.

Test environment boundary

The sandbox permits ten verified contacts and omits webhooks. It is therefore not a full substitute for testing a production event pipeline. Agree on an evaluation environment with the events and account scope your implementation will actually use.

Questions for procurement

Request the rate and new-contact limits, support coverage, number ownership terms and paid integration scope in writing. Keep API acceptance, message delivery and user read status distinct in the application. We have not measured those states against live customer traffic. Public integration listings establish options to investigate, not parity across every supported CRM.

Check Sendblue directly ↗

Source notes

  1. Plans and sandbox
  2. Integrations