Cloud PBX
Open for Nextiva
Route a Nextiva auto-attendant branch or call queue to Open and the AI picks up — Nextiva stays your phone system.
- Setup time
- Under 20 minutes
- Auth
- Digest credentials or IP allowlist
- Directions
- Inbound · Outbound · Call transfer
- Pricing
- Included with Open
01 — Overview
Can I add an AI phone agent to my Nextiva phone system?
Yes. Your Nextiva extensions, voicemail, and Auto Attendant stay in place. Open is a SIP destination one or more of your queues route to when you want AI on a specific call class.
Nextiva remains the phone system. Users, extensions, voicemail, recording, and the NextOS admin console all stay where they are. Open joins as a SIP destination — practically that means a forwarding rule on a queue or Auto Attendant branch that sends inbound legs to Open. The calls you opt-in to AI flow through Open; everything else keeps working untouched.
For Nextiva Cloud PBX, the typical path is to forward a call queue or specific DID to a SIP URI that points at Open. Nextiva supports external SIP forwarding via Call Forwarding rules and Auto Attendant 'Transfer to External' actions on appropriate plans.
For Nextiva Contact Center, Open is added as an external routing target on a queue or skill. When a call matches the routing condition, NextOS hands the leg to Open via SIP, the AI handles the conversation, and escalations transfer back into a queue via SIP REFER with the live transcript attached.
What the AI does on the call: it listens, reasons over your knowledge base and connected tools (Salesforce, HubSpot, Zendesk, calendar, payments), and acts — looking up records, creating tickets, scheduling callbacks, or warm-transferring to a human Nextiva agent.
Billing stays predictable. Nextiva continues to invoice your seats and minutes. Open charges per resolved conversation, with no markup on Nextiva minutes and no extra Nextiva seats needed for an AI front-line.
What stays the same on Nextiva
Nextiva users and extensions
Seats, IVRs, voicemail, and recording rules don't change.
Numbers and DIDs
All your Nextiva numbers stay on Nextiva.
NextOS admin console
You manage everything the same way as today.
Reporting
NextOS analytics keep working unchanged.
What's new with Open
A SIP forwarding rule
On the queue or Auto Attendant branch you want AI'd, you add Open as the destination.
AI handles the conversation
The AI greets, listens, calls your tools, and replies in natural speech.
Transfers carry context
Escalations to Nextiva agents receive the live transcript.
Pricing model
You pay Open per resolved conversation — no extra Nextiva seats needed.
02 — Why this works
The native Nextiva experience
No new seats just for AI
An AI front-line isn't a user — you don't expand Nextiva seat count.
Per-queue opt-in
Pick exactly which queues or Auto Attendant branches get AI.
Cloud PBX + Contact Center, both work
Whether you live in Nextiva Cloud PBX or Contact Center, Open slots in as a destination either way.
Warm transfer back to your Nextiva agents
When the AI escalates, your existing Nextiva agents receive the call with the live transcript.
03 — Setup guide
Wire up Nextiva in under 20 minutes
Two trunks — one inbound, one outbound. Both configurable from Settings → SIP in the Open dashboard.
- 1
Open Settings → SIP
Open the inbound trunk configuration.
- 2
Pick a SIP region
Choose Global or US.
- 3
Copy the SIP credentials
Grab the SIP endpoint, username, and password.
- 4
Pick the Nextiva target
Decide which queue or Auto Attendant branch should route to AI.
- 5
Add Open as a SIP destination
In NextOS: queue → Forwarding → External SIP URI. For Auto Attendant: branch → Transfer to External → SIP URI.
- 6
Add the matching numbers to Open
Under Phone Number (DID), add the Nextiva DIDs that fronted the queue.
- 7
Assign numbers to an AI agent
Channels → Phone → Agents → assign DIDs.
- 8
Place a test call
Dial a Nextiva number and confirm Open answers.
04 — Configuration
Settings → SIP, at a glance
A real inbound trunk for Nextiva looks something like this. Yours are generated when you open Settings → SIP.
Inbound trunk · Nextiva
Sample
- SIP endpoint
- sip.us.opencx.comUS region
- Transport
- TLSrecommended
- Username
- open_inbound_nxtv…
- Password
- ••••••••••••••••
- Nextiva target
- Queue / Auto Attendant
05 — Security
Encrypted, audited, refundable
SIP over TLS for signaling, SRTP for media. Every call is logged with full reasoning traces. SOC 2 Type II, GDPR-aligned, HIPAA- and PCI-ready. Backed by the Open $2M Refund Guarantee.
06 — FAQ
