Cloud PBX
Open for RingCentral
Route a RingCentral queue, IVR branch, or RingCX skill to Open and the AI picks up — without leaving your RingCentral admin console.
- Setup time
- Under 20 minutes
- Auth
- Digest credentials, IP allowlist, or BYOC SBC pairing
- Directions
- Inbound · Outbound · Call transfer
- Pricing
- Included with Open
01 — Overview
Can I add an AI phone agent to my RingCentral phone system?
Yes. Your RingCentral system stays as-is — extensions, IVRs, dial plans, voicemail. Open is a SIP destination your queues, IVR branches, or RingCX flows route to when you want AI to take a specific class of calls.
RingCentral remains the phone system. Users, extensions, dial plans, voicemail, recording rules, and the RingEX admin console all stay where they are. Open joins as a SIP destination — practically that means a SIP-forwarding rule on a queue, a 'Transfer to External' branch in your IVR, or a routing destination in RingCX. The calls you opt-in to AI flow through Open; everything else keeps working untouched.
For RingEX (the unified app + cloud PBX), the cleanest pattern is to forward a specific queue, group, or DID to a SIP URI that points at Open. RingCentral supports forwarding to external SIP via call queue setup or via the BYOC (Bring Your Own Carrier) program where you bring a partner trunk. Either way, the inbound INVITE lands on Open, the AI picks up, and the rest of the conversation runs over standard SIP/RTP.
For RingCX (the contact-center product), Open is configured as an external routing destination on a skill or queue. When a call matches that skill, RingCX hands the leg to Open via SIP, the AI handles the conversation, and any escalation transfers back into a RingCX skill via SIP REFER — bringing the live transcript and detected intent with it.
What the AI does on the call: it listens, reasons over your knowledge base and connected tools (Salesforce, HubSpot, Zendesk, Shopify, Stripe, Calendar), and acts — looking up records, creating tickets, scheduling callbacks, sending payment links, or warm-transferring to a human RingCentral or RingCX agent with the live transcript attached. Every call is recorded and trace-logged.
Billing stays predictable. RingCentral keeps invoicing your RingEX/RingCX seats. Open never marks up RingCentral minutes; it charges per resolved conversation. You don't need to add seats to give a queue an AI front-line — the AI is one destination, not 50 new users.
What stays the same on RingCentral
RingCentral users and extensions
Existing seats, IVRs, dial plans, and voicemail rules don't move.
Numbers and DIDs
All your RingCentral numbers stay on RingCentral. No porting required.
RingEX admin console
You manage extensions, queues, and policies the same way you do today.
Reporting and analytics
Call logs and reporting in RingCentral continue. Open adds AI-side reasoning traces on top.
What's new with Open
A SIP forwarding rule
On the specific queue, IVR branch, or RingCX skill 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 back to a human RingEX/RingCX agent receive the live transcript and detected intent.
Pricing model
You pay Open per resolved conversation — no extra RingCentral seats needed for an AI front-line.
02 — Why this works
The native RingCentral experience
No new seats just for AI
An AI front-line on a queue isn't a user — you don't need to expand your RingCentral seat count to give every queue an AI agent.
Per-queue, per-IVR opt-in
Pick exactly which queues, IVR branches, or RingCX skills get AI. The rest of your phone system stays untouched.
RingEX + RingCX, both work
Whether you're on RingCentral's MVP/RingEX or RingCX contact center, Open slots in as a SIP destination either way.
Warm transfer back to your RingCentral agents
When the AI escalates, your existing RingCentral or RingCX agents receive the call with the live transcript and detected intent.
03 — Setup guide
Wire up RingCentral 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 in OpenCX.
- 2
Pick a SIP region
Choose Global, US, EU, or APAC.
- 3
Copy the SIP credentials
Grab the SIP endpoint, username, and password.
- 4
Pick the RingCentral target
Decide which queue, IVR branch, or RingCX skill should route to AI. You can start with one and expand later.
- 5
Add Open as a SIP destination
In RingEX: queue → Forwarding → External SIP URI; or BYOC carrier route. In RingCX: skill → Routing → External SIP destination.
- 6
Add the matching numbers to Open
Under Phone Number (DID), add the RingCentral DIDs that fronted the queue or IVR.
- 7
Assign numbers to an AI agent
Channels → Phone → Agents → assign DIDs.
- 8
Place a test call
Dial a RingCentral number and confirm Open answers when the queue/IVR branches to AI.
04 — Configuration
Settings → SIP, at a glance
A real inbound trunk for RingCentral looks something like this. Yours are generated when you open Settings → SIP.
Inbound trunk · RingCentral
Sample
- SIP endpoint
- sip.us.opencx.comUS region
- Transport
- TLSrecommended
- Username
- open_inbound_rc…
- Password
- ••••••••••••••••
- RC target
- Queue / IVR / RingCX skill
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
