200ms agents beside Five9.
Bland's self-hosted voice stack answers in 200 milliseconds, and our FDE team takes deployments live in 30 days, connected to Five9 over standard SIP.
Bland + Five9
Run Bland voice agents alongside Five9 over standard SIP: routine calls answered in 200ms, complex ones handed to Five9 agents, live in 30 days.
What Bland does inside Five9.
Runs alongside Five9.
Bland deploys next to Five9 over a SIP trunk, so there is no cutover. Send a subset of calls to Bland and widen it as results come in.
Routine calls answered by AI.
Calls you route to a Bland number or DID are answered by a voice agent that runs your pathway, calls your APIs, and writes results back.
Account data before hello.
Create an inbound session with request data, pass its token in the x-bland-session-id SIP header, and the agent knows who is calling.
Warm hand-off to Five9 agents.
When a call needs a person, the agent briefs whoever answers on a Five9 DID or SIP URI, then joins the caller and steps back.
Failover built into the trunk.
Primary, secondary, and tertiary SIP servers with automatic failover and failback keep calls flowing if one endpoint goes down.
How it deploys.
Open the SIP Setup Wizard from your Bland dashboard.
Enter your Five9 SIP endpoint and let auto-discovery probe the connection.
Allow-list Bland's static signaling and media IPs in your Five9 firewall.
Run a test call from the wizard to verify the trunk.
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 AI voice agents work with Five9?
Yes. Bland connects to Five9 over standard SIP trunking, with no plugin to install. Bland answers the calls Five9 routes to it, runs the conversation, and transfers callers back to Five9 when a human is needed.
Can Bland run alongside Five9?
Yes. Bland can be deployed alongside Five9 in a hybrid model, so there is no need for a full cutover. Start by routing a subset of calls to Bland and expand as it proves out.
How does a call get from Bland back to a Five9 agent?
A Transfer Call node targets a DID or SIP URI on your trunk. With warm transfer on, Bland calls the Five9 side first, briefs the person who answers on the caller and context, then merges the calls and steps out.
Can Five9 send caller context to the Bland agent?
Yes. Create a session with the Bland Create Inbound Session API and the variables you want, then send its token as the x-bland-session-id SIP header on the call into Bland. The agent reads those variables from the first turn.
What security does the SIP connection use?
Every connection is encrypted: SIP signaling over TLS on port 5061 and audio over SRTP, from static IPs you allow-list. 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.