One agent across voice and text.
The pathway or persona that answers your phones also answers texts, with the same tools and memory, on a platform that is SOC 2 Type II and HIPAA ready. Voice cues are stripped from replies automatically.
One Bland agent across voice, SMS, and RCS, with the same pathways, tools, and memory on every channel, on a SOC 2 Type II and HIPAA ready platform.
The pathway or persona that answers your phones also answers texts, with the same tools and memory, on a platform that is SOC 2 Type II and HIPAA ready. Voice cues are stripped from replies automatically.
Numbers with an RCS profile send a verified business profile, suggested replies, action buttons, cards, and media. Recipients without RCS get the same conversation over SMS.
With memory on, a contact who called yesterday and texts today is recognized as the same person, with one history of facts, summaries, and open items.
Text conversations run the same tools, outcomes, citations, and summary prompts as calls. When a thread ends, the webhook carries the transcript, variables, tags, and summary.
A Transfer to Human node or an API call hands the conversation to a rep, who replies from the same number. Resume the agent at any node, or end the thread.
Numbers bought from Bland are linked to a Twilio Messaging Service for you. For bring-your-own Twilio numbers, register the A2P campaign in Twilio and enter the Messaging Service SID in Bland.
Pick or buy a number in the messaging dashboard and attach a pathway or persona.
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.
For BYOT, set up your A2P campaign in Twilio and pass the Messaging Service SID.
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.
MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly.
Yes. Attach the same pathway or persona to a messaging number and it handles SMS and RCS with the same logic, tools, and memory it uses on calls. Voice cues are stripped so texts read cleanly, and our FDE team sets up messaging as part of your Enterprise plan.
Both run through the same Bland endpoints. RCS adds a verified business profile, suggested replies, action buttons, cards, and media. When a number has an RCS profile and the recipient's phone supports it, Bland sends RCS; otherwise it falls back to SMS.
Yes. Every US number that sends SMS needs an A2P campaign. Numbers bought from Bland are registered and linked to a Messaging Service for you. For your own Twilio numbers, register the campaign in Twilio and enter the Messaging Service SID in Bland.
Yes. A Transfer to Human node in the pathway, or a handoff API call, stops the agent replying. Your rep answers from the same number, so the customer sees one thread. You can then resume the agent at a specific node or end the conversation.
Set a webhook on the number. When a conversation ends, Bland posts the transcript, pathway variables, tags, metadata, and any configured summary, citations, and outcomes, with a channel field so you can route SMS, RCS, iMessage, and WhatsApp events separately.
See every integration on the integrations hub.
They map Bland to your stack, design the rollout, and stay on through go-live. Enterprise deployments go live in 30 days.
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.