One agent on calls and WhatsApp.
Personas attach to voice, SMS, and WhatsApp numbers through the same endpoint, so the agent that answers your phones answers WhatsApp too, on a SOC 2 Type II and HIPAA ready platform.
Bland + WhatsApp
Run the same Bland agent on calls and WhatsApp, with shared personas, per-number context, and conversation webhooks on a SOC 2 Type II platform.
What Bland does inside WhatsApp.
Context per number.
Request data on each WhatsApp number gives the agent key-value facts, like a facility ID or opening hours, so one agent can serve many locations.
Reply timeouts.
Set how many seconds the agent waits for a reply before the conversation times out, per WhatsApp number.
Webhooks per number.
Each WhatsApp number posts message and status events to its own webhook URL, with a channel field set to whatsapp for routing.
The same Messaging API.
WhatsApp conversations run through the endpoints that serve SMS, RCS, and iMessage. List WhatsApp numbers with channel=whatsapp.
Read receipts.
Message status on WhatsApp includes read, alongside queued, sent, delivered, failed, and undelivered.
How it deploys.
Turn on messaging.
Your account executive switches on messaging for your organization as part of Bland Enterprise.
Set up the WhatsApp channel.
At All agents, open Phone numbers, configure the number, and choose Set up on the WhatsApp channel.
Configure the WhatsApp drawer.
Set the webhook URL, the reply timeout in seconds, and any request data the agent should know, then select Save.
Assign the agent and test.
Assign the agent or persona that should answer, then send a message from WhatsApp and check the webhook.
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.
Can Bland run an AI agent on WhatsApp?
Yes. WhatsApp is one of Bland's messaging channels, alongside SMS, RCS, and iMessage. A WhatsApp number runs the same agent or persona as your voice line, with its own webhook, reply timeout, and request data, set up as part of Bland Enterprise.
How does the agent know which location a WhatsApp number belongs to?
Set request data on the number: key-value facts such as a facility ID or its opening hours. The agent sees both the keys and the values in every WhatsApp conversation on that number, so one agent can serve many numbers.
How do I get WhatsApp conversation data into my systems?
Give the WhatsApp number a webhook URL. Bland posts message and status events there, and payloads carry a channel field set to whatsapp, so one handler can route WhatsApp, SMS, RCS, and iMessage events separately.
Is the WhatsApp API different from the Bland SMS API?
No. WhatsApp shares the Bland Messaging API with SMS, RCS, and iMessage. Conversations report a whatsapp effective channel, numbers list with channel=whatsapp, and message status includes read receipts on WhatsApp.
Who sets up a WhatsApp agent?
Our FDE team scopes the deployment, enables messaging for your organization, 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.