Bland + Genesys

Connect Genesys over standard SIP with no plugin to install, and put 200ms Bland voice agents in front of your queues, with warm transfers back to agents.

Book a call Read the docs

What Bland does inside Genesys.

Works with your Genesys trunk today.

Bland connects over standard SIP, so it plugs into the Genesys telephony you already run with no plugin to install. Genesys keeps routing and queues, and Bland agents answer in 200 milliseconds.

Calls in from your flows.

Route the calls you want automated from Genesys to a number or DID on the Bland trunk, and the agent you assign answers with its pathway.

Context arrives with the call.

Create an inbound session with customer data before routing the call, and send its token as the x-bland-session-id SIP header. The agent starts with the account in hand.

Back to a human when needed.

A Transfer Call node sends the caller to a Genesys DID or SIP URI by SIP REFER, a new INVITE, or a warm transfer that briefs the agent first.

Outbound through the same trunk.

Use a number on the trunk as the from value on a Bland call request, and agent calls go out through your Genesys telephony.

SIP traces for your telecom team.

Every call on the trunk has a full SIP ladder with headers and SDP, so you can see exactly which leg failed and why.

How it deploys.

Open the SIP Setup Wizard from your Bland dashboard.
Enter your Genesys SIP endpoint and let auto-discovery probe the connection.
Allow-list Bland's static signaling and media IPs in your Genesys 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.

Talk to an FDE

Drop Bland into your editor.

MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly.

1
2
3
4
5
6
7
8
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"
  }'

Visit Trust and Security Portal

Frequently asked questions.

How does Bland integrate with Genesys?

Over standard SIP trunking, so it works with the Genesys telephony you already run, with no plugin to install. You build a trunk in Bland's SIP setup wizard, point it at your Genesys SIP endpoint, attach numbers or DIDs, and route calls between the two platforms in both directions.

Can Bland hand a call back to a Genesys queue?

Yes. A Transfer Call node can target a DID, extension, or SIP URI on your trunk, so the caller lands on the number or address that feeds your Genesys queue. Warm transfer briefs the human agent before the caller joins.

Can Genesys pass customer data to the Bland agent?

Yes, through a SIP header. Create an inbound session through the Bland API with the variables you want, then include the returned token as the x-bland-session-id header on the call into Bland. The agent can use those variables immediately.

What does Bland handle and what stays in Genesys?

Bland runs the automated conversation: the voice agent, its tools, and the data it writes back. Genesys keeps routing, queues, and your human agents. Most teams start by routing a subset of calls to Bland and expand from there.

What network setup does the trunk need?

Allow-list Bland's static signaling and media IPs for your region. SIP signaling runs over TLS on port 5061 and media over SRTP on UDP 16384 to 32768, so the Genesys side must support both.

Who actually wires this up?

Our FDE team scopes the integration, maps Bland to your call flows, and stays on through go-live. Enterprise deployments go live in 30 days.