Bland + Bandwidth

Run Bland voice agents on your Bandwidth numbers over SIP, with a carrier-grade network underneath and a clean handoff to your contact center.

Book a call Read the docs

What Bland does inside Bandwidth.

Your carrier, Bland's voice stack.

Your numbers stay on Bandwidth while Bland runs speech recognition, the language model, and voice on its own infrastructure, responding in 200 milliseconds.

A network Bandwidth owns.

Bandwidth owns and operates its network, so there are fewer hops between your caller and your agent. Core network uptime is 99.999%.

Numbers, porting, and routing in one place.

Port your numbers to Bandwidth or order new ones, then manage them and their routing in the Bandwidth App. No separate number vendor to juggle.

Configuration, not code.

Set up a SIP endpoint in Bandwidth and a trunk in Bland. There's no application to write or host.

Encrypted signaling and media.

Signaling between Bandwidth and Bland runs over TLS, and call audio is encrypted with SRTP. Bandwidth has already handled the firewall setup, so there's nothing to allow-list.

Carrier-layer routing and handoff.

Calls reach your agent at the carrier layer, so an outage on your contact center platform doesn't take your voice AI down. When a caller needs a person, Bland transfers them to your contact center.

How it deploys.

Create your Bandwidth SIP endpoint.
In the Bandwidth App, add a SIP realm. Copy the FQDN Bandwidth generates, then add the port from your trunk group configuration.
Route your number to Bland.
Create a Voice Configuration Package that routes to Bland's SIP URI, then assign your number to it. For outbound calls, add a SIP credential to your realm.
Create the trunk in Bland.
Go to Phone Numbers, then SIP, then Create Trunk. Enter your Bandwidth SIP endpoint. Bandwidth has already configured the firewall, so just confirm the box. Add your SIP credentials for outbound.
Add your numbers.
Enter each Bandwidth number in E.164 format, save the trunk, and your agent can answer and place calls on it.

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.

Can I use Bandwidth numbers with a Bland AI voice agent?

Yes. Connect Bandwidth to Bland with a SIP trunk. Route your Bandwidth numbers to Bland, and your agents answer inbound calls and place outbound calls on them.

Can I keep my numbers on Bandwidth?

Yes. A SIP trunk carries your numbers on your own carrier, so they stay on Bandwidth. Calls reach your Bland agent over Bandwidth's network. Don't have numbers yet? You can also order new ones from Bandwidth.

What do I need before I start?

A Bandwidth Universal Platform account with Bland interconnect enabled, and a Bland account with SIP trunking on. To enable interconnect, open a ticket with your Bandwidth account representative and name the admin who will configure it.

Do I need to write or host any code?

No. The integration is entirely configuration: a SIP realm and credentials in Bandwidth, and a SIP trunk in Bland.

What happens if my contact center platform goes down?

Routing happens at the carrier layer, so calls can still reach your Bland agents.