Partners · Sendblue
Real iMessage, not just SMS.
Real iMessage and SMS to your clients -- blue bubbles, expressive effects, true two-way conversations.
messaging.smsmessaging.imessagemessaging.mmsmessaging.group
About
Sendblue is the messaging partner PeptideClients connects to for client SMS and iMessage. Bring your own Sendblue account; PeptideClients handles the template rendering, opt-in tracking, segment-level usage, and two-way inbox. Outbound goes through your Sendblue line so every message carries your sender reputation. Inbound lands on the matched client's timeline automatically.
What's connected
Real iMessage with fallback
Send true blue-bubble iMessages with automatic SMS fallback for non-Apple recipients. The choice happens at delivery time; you do not pick the channel.
Two-way inbox
Inbound SMS and iMessage land on the matched client's timeline automatically and surface as an unhandled-message queue for the team.
Expressive effects
Per-template send styles -- celebration, confetti, lasers, fireworks -- when the recipient is on iMessage. Plain SMS for everyone else.
Per-segment usage + hard caps
Every outbound segment is logged with its actual cost. Set monthly caps per org or per store; hard-enforced before the send hits Sendblue.
TCPA-grade opt-in tracking
Per-(phone, org) consent state with STOP/HELP keyword handling honored automatically. Marketing sends never bypass the opt-out flag.
Per-org / per-store credentials
Your Sendblue API keys are stored in Supabase Vault, scoped per organization or per store. Workspaces never share each other's sender reputation.
Use cases
Patient coordinator
iMessage a refill reminder
Send a friendly check-in with a celebration effect to clients on iMessage; SMS fallback for everyone else -- one template, both channels.
Compliance officer
Per-workspace opt-out trail
Every STOP keyword updates the per-org consent state; every send checks it before going out. Audit-ready trail without spreadsheets.
Owner
Cap SMS spend per store
Set the monthly segment cap at the store level so a runaway template can never blow up the bill. Cap exhaustion fails-loud at queue time, not on the invoice.
FAQ
Do I need a Sendblue account?
Yes. You bring your own Sendblue account so messaging cost and sender reputation stay with you. Get one at sendblue.com.
Can I send from different numbers per store?
Yes. Connect a separate Sendblue API key + from-number per store; the platform routes sends to the right line based on the originating workspace.
What about STOP / HELP keywords?
Handled automatically. STOP marks the (phone, org) pair opted-out; subsequent sends in that workspace will refuse to queue. System-class sends (account / auth) still go through.
How is iMessage vs SMS decided?
Sendblue decides at delivery time based on whether the recipient has iMessage enabled. The template just specifies optional expressive effects that only render on iMessage.
How is cost tracked?
Per outbound segment. The Sendblue webhook reports the real segment count and message kind; the platform locks the cost onto the message row and rolls it up monthly per org/store.
Wire up Sendblue from your settings.