200ms agents on RingCentral numbers.
Bland's self-hosted voice stack responds in 200 milliseconds and connects to RingCentral over a standard SIP trunk, with no app to install.
Bland + RingCentral
Put Bland's 200ms voice agents on your RingCentral numbers over a standard SIP trunk, with no app to install and transfers back to your team.
What Bland does inside RingCentral.
A guided RingCentral entry.
RingCentral is in the SIP setup wizard's provider catalog. Enter the SIP endpoint from your RingCentral account and the wizard parses host, port, and transport.
Your numbers, answered by AI.
Attach the RingCentral numbers you want automated to the trunk. Each one behaves like any Bland inbound number, with its own pathway, persona, and voice.
Outbound on your caller ID.
Use a trunk number as the from value on a Bland call request and the agent dials out through RingCentral.
Hand-offs to your people.
Transfer Call nodes route a caller to a phone number, DID, or SIP URI, with warm transfer to brief the person who picks up.
Traces for every call.
Each call keeps a SIP ladder with headers and SDP, plus direction, status, response code, and duration.
How it deploys.
Start a trunk.
At All agents, open Dispatch, then Phone numbers, then SIP, click Add trunk, and choose RingCentral.
Enter the endpoint.
Paste the SIP endpoint from your RingCentral account and let discovery recommend port and transport.
Authenticate.
Allow-list Bland's signaling and media IPs if needed, then choose IP-based or registration-based auth and save the trunk.
Attach numbers and test.
Attach the RingCentral numbers the agent should answer, press Test connection, and call one of them.
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 I add an AI voice agent to RingCentral?
Yes, over SIP. RingCentral is one of the guided providers in the Bland SIP setup wizard. You enter your RingCentral SIP endpoint, finish authentication, and attach the numbers a Bland agent should answer or call out from.
What does the RingCentral connection run on?
A standard SIP trunk, so your RingCentral numbers connect with no app to install and get the same setup wizard, warm transfers, SIP traces, and failover as every Bland SIP connection.
Can the AI agent transfer callers to my RingCentral users?
Yes. A Transfer Call node can send the caller to a phone number, or to a DID or SIP URI on the trunk. Turn on warm transfer and the agent briefs the person who answers before connecting the caller.
Which RingCentral numbers can I use?
The numbers you already own. The SIP trunk carries your RingCentral numbers as they are, so attach the ones you want the agent on. You can also port numbers to Bland if you would rather move them.
How secure is the connection?
Bland encrypts every connection, with SIP over TLS on port 5061 and audio over SRTP. Bland is SOC 2 Type II and HIPAA ready, and call data is encrypted in transit and at rest.
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.