Bland announces a Series C with over $100M raised.

Bland + SMS & RCS

Conversational SMS that upgrades to rich RCS automatically, on the same pathways, personas, and memory as voice. Available on Enterprise plans.

SMS & RCS

What Bland does inside SMS & RCS.

Automatic upgrade to RCS when supported

Verified profile, buttons, and cards on RCS

Shared memory with voice agents

A2P handled for Bland numbers; BYOT supported

How it deploys.

  1. Pick or buy a number in the messaging dashboard and attach a pathway or persona.

  2. For Bland numbers, A2P registration and the Twilio Messaging Service link are handled for you. Work with your AE to add an RCS profile for rich messaging.

  3. For BYOT, set up your A2P campaign in Twilio and pass the Messaging Service SID.

  4. Bland sends RCS when the recipient supports it and falls back to SMS automatically.

Our FDE team scopes the integration, maps Bland to your stack, and stays on through go-live. Enterprise deployments go live in 30 days.

Drop Bland into your editor.

MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly.

curl -X POST https://api.bland.ai/v1/calls \
-H "Authorization: $BLAND_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"phone_number": "+14155552120",
"task": "Qualify refi lead",
"voice": "june"
}'

Frequently asked questions.

Is SMS & RCS available on every plan?

Messaging is an Enterprise feature. Talk to your account executive or book a demo to switch it on.

How is SMS & RCS priced?

Messaging is priced separately from per-minute voice, billed per message on SMS. Enterprise deals are contracted; talk to our team for a quote.

Can the agent remember a voice call when the customer messages back?

Yes. With memory on, the same contact is recognized across voice, SMS, RCS, and iMessage, with one history of facts, summaries, and open items.

How is conversation data secured with SMS & RCS?

Bland is SOC 2 Type II and HIPAA ready. Conversation data is encrypted in transit and at rest. Enterprise plans support optional residency controls.

Who actually wires this up?

Our FDE team scopes the integration, maps Bland to your stack, and stays on through go-live. Enterprise deployments go live in 30 days.

Related integrations.

See every integration on the integrations hub.

With our team

Our FDE team scopes the integration with you.

They map Bland to your stack, design the rollout, and stay on through go-live. Enterprise deployments go live in 30 days.

On your own

Or drop Bland into your editor.

The Bland MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly. Free sandbox, no credit card.