A supported carrier for Bland.
NICE CXone is a supported bring-your-own-carrier SIP provider for Bland Enterprise, so CXone calls reach agents that respond in 200 milliseconds on Bland's self-hosted stack.
Bland + NICE CXone
NICE CXone is a supported carrier for Bland, so 200ms AI voice agents take CXone calls over SIP and hand them back to your team with full context.
What Bland does inside NICE CXone.
Agents on both directions.
Bland answers calls CXone routes to it, and places outbound calls through the trunk when a trunk number is the from value.
Context in the SIP header.
An inbound session token in the x-bland-session-id header carries account data into the call, so the agent picks up with what CXone already knows.
Hand-offs to your team.
Transfer to a CXone DID or SIP URI by SIP REFER, by a new INVITE from Bland, or by a warm transfer with a spoken briefing.
Codecs your SBC expects.
Reorder or disable PCMU, PCMA, Opus, G.722, and G.729 per number, with optional transcoding.
Diagnostics on the trunk.
Test connection sends a SIP OPTIONS ping over TLS, and per-call traces show the full ladder with headers and SDP.
How it deploys.
Open the SIP Setup Wizard from your Bland dashboard.
Enter your NICE CXone SIP endpoint and let auto-discovery probe the connection.
Allow-list Bland's static signaling and media IPs in your NICE 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.
Does Bland work with NICE CXone?
Yes. NICE CXone is a supported bring-your-own-carrier SIP provider for Bland Enterprise. Calls move between CXone and Bland over a standard SIP trunk built with the Bland setup wizard, in both directions.
Can a Bland agent transfer a caller to a CXone agent?
Yes. A Transfer Call node can send the caller to a DID or SIP URI on your trunk. Warm transfer calls the CXone side first, briefs the person who answers, then merges the caller in, so nobody repeats themselves.
How does caller context reach the Bland agent?
Before routing the call, create an inbound session through the Bland API with the variables you want the agent to know. Send the returned token as the x-bland-session-id SIP header and the variables load into the call.
What does the SIP connection require on the NICE side?
Support for SIP over TLS on port 5061 and SRTP media, plus allow-listing Bland's static signaling and media IPs for your region. Discovery in the setup wizard reports the port, transport, and codecs it finds.
Who actually wires this up?
Our FDE team scopes the integration, maps Bland to your CXone call flows, 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.