You add a Bland AI phone agent to Five9 by ordering AI Agent Connect through your Five9 account team, routing numbers over a SIP trunk to Bland, and assigning an agent to each number in Bland's dashboard. SIP is how a contact center connects to Bland, and a trunk is one such connection, set up once.
Bland is an accredited Five9 AI Agent Connect partner and a NICE DEVone technology partner. Setup runs Five9 first and Bland second, in the order of Bland's Five9 setup guide.
What do you need before you start?
Before a Five9 call can reach a Bland agent, you need three things: a Five9 contact center (VCC) account and your Five9 account team, a Bland account with SIP trunking enabled, and a Bland agent ready to answer. If there is no SIP tab under Phone numbers in your Bland account, contact Bland support.
Put your agent in production first, because an agent that has not been promoted to production cannot take a call from anyone else. Building your first AI phone agent covers that, and Five9's interop test exercises the real conversation.
How a call moves between Five9 and Bland
Your Five9 account team and Five9 Professional Services work with you on the Five9 side, Bland's account team attaches your numbers, and your team finishes in Bland's dashboard by assigning an agent to each number, adding a transfer back to Five9, and mapping call data to SIP headers, which are labeled fields that travel with a call.
Bland's SIP connection is built and tested once in Five9's partner environment and reused for each customer. Calls go from Five9 to a Bland agent and transfer back to Five9 skills or agents, with call data in SIP headers.
To hand back, a Transfer Call node sends the caller to a Five9 number, and Bland places a new call to Five9 (a SIP INVITE) over the same trunk and bridges the audio.
How do you add a Bland AI phone agent to Five9?
You add a Bland AI phone agent to Five9 in two parts: four steps in Five9, then three in Bland.
Order and configure Five9
Order AI Agent Connect. Ask your Five9 account team for a quote for AI Agent Connect, with Bland as the AI agent partner. If you are not a Five9 customer yet, your Bland account team can register the opportunity with Five9. Five9 then opens a project, and Five9 Professional Services works with you on the IVR script.
Give Five9 the Bland connection details. Five9 Professional Services and your Five9 administrator need these six items:
- Endpoint: your Bland region, for example
us2.sip.bland.ai. The other regions are under Connection endpoints. - Transport: TLS 1.2 or higher, port 5061.
- Media: SRTP (
AES_CM_128_HMAC_SHA1_80), UDP 16384 to 32768. - Trusted peers: all six Bland IPs for your region, covering both signaling and media.
- Certificate: Let's Encrypt. The ISRG Root X1 CA must be trusted.
- Number format: E.164 or 10-digit. Bland accepts both.
- Endpoint: your Bland region, for example
Route calls to Bland in Five9. Label the numbers that should reach Bland so they route over the Bland SIP trunk, not the PSTN (the public phone network). In your IVR script, send calls to those numbers where the agent should take over.
Tell Bland which numbers to use. Send your Bland account team the numbers Five9 will route to Bland, and the Bland organization they belong to. Bland attaches them to your organization and allow-lists Five9's SIP addresses. Also note the Five9 numbers or skills your agent should transfer callers back to.
Configure Bland
Assign an agent. Once Bland attaches your numbers, go to All agents, then Dispatch, then Phone numbers. Press Configure on each number and pick the agent under Assignment.
Add the transfer back to Five9. In the agent, add a Transfer Call node that sends the caller to the Five9 number for the right skill.
Pass call data to the Five9 agent. To hand over details such as an account number or the reason for the call, map call variables to SIP headers in the Headers section of the trunk's Configure tab.
How do you know your Bland and Five9 connection worked?
Your Bland and Five9 connection worked when it passes Five9's interop test, which Five9 requires before it allows go-live, and each test call shows up on the trunk's Overview tab in Bland. Plan the test around four things:
- Real test numbers, labeled for the Bland trunk on your Five9 domain. Five9 doesn't accept Twilio numbers or Five9-owned numbers as test numbers.
- Every call path. When Five9 assigns a primary and a secondary session border controller (SBC), test through both.
- The whole call: two-way audio, DTMF, hold, and a transfer back to a live Five9 agent.
- A Five9 user logged in as an agent, so transfers back to Five9 have someone to land on.
Compare each test call's SIP trace on the trunk's Overview tab with Five9's logs.
What can go wrong when Five9 sends calls to Bland?
Seven common failures come up when Five9 sends calls to a Bland agent, each with its fix.
- Five9's SIP OPTIONS ping to Bland times out. Bland doesn't have Five9's current SBC IPs, or Five9 is pinging over UDP or port 5060. Send Bland the current SBC IPs, and check Five9 sends TLS to port 5061.
- Calls are rejected with 603 Decline. The number isn't attached to your Bland organization. Send it to your Bland account team.
- Calls go to Five9 voicemail or stay inside Five9. The number is still an internal Five9 inbound number. Re-label it in Five9 so it routes out the Bland trunk.
- Test calls go over the phone network instead of the trunk. The test number isn't routed over the trunk on both sides. Label it for the Bland trunk in Five9, and confirm Bland attached it.
- Calls drop mid-call with 481 Call/Transaction Does Not Exist. Five9 has Bland's IPs on more than one trunk. Ask Five9 to keep them on a single trunk.
- The call connects with no audio. SRTP isn't on, or Bland's media IPs aren't trusted. Enable SRTP toward Bland, and trust all six Bland IPs for your region.
- The transfer back to Five9 fails or lands in the wrong queue. The transfer number isn't routed to a skill in the Five9 script. Check the script, and that a Five9 agent with that skill is logged in.
What comes next after Five9 reaches your Bland agent?
Once Five9 reaches your Bland agent, adding knowledge to an AI phone agent shows how a Bland agent answers from your own content, and testing an AI phone agent before launch follows. Bland with Five9 covers how a Bland agent works in front of, or alongside, a Five9 contact center. See the no-code AI call center guide and no-code AI phone agents hub.
Idaho Housing and Finance Association saves $750,000 a year by replacing its IVR with Bland, which handles 4,000 inbound calls a day and cut average call time by 20%.
"We save thousands of dollars a day."
Greg Blake, Chief Information Officer, Idaho Housing and Finance Association
Frequently asked questions
Does Bland have a no-code option?
Yes. Norm, Bland's AI assistant, builds voice agents using natural language descriptions, and Bland's dashboard includes a visual builder for non-technical users.
Is Bland a Five9 partner?
Yes. Bland is an accredited Five9 AI Agent Connect partner and a NICE DEVone technology partner.
What does Five9 do and what does Bland do when Five9 sends calls to Bland?
Five9 routes calls to Bland over a SIP trunk, a Bland agent handles the conversation, and when a person is needed the Bland agent transfers the caller back into Five9. Five9 Professional Services works with you on the IVR script, and your Bland account team attaches your numbers to your Bland organization.
How does Bland's SIP connection to Five9 work for each customer?
Bland's SIP connection is built and tested once in Five9's partner environment and reused for each customer. Each Five9 customer orders AI Agent Connect through its Five9 account team, gives Five9 the Bland connection details, and sends its Bland account team the numbers Five9 will route to Bland.
Can a Bland agent transfer callers back to Five9?
Yes. A Bland agent uses a Transfer Call node that sends the caller to the Five9 number for the right skill, and a Five9 agent with that skill must be logged in.
