Quick answer: Yes, by five routes. RingCentral AIR (from US$39 a month as a RingEX add-on) and Zoom Virtual Agent Receptionist (from US$0.25 a minute billed annually, plus Zoom Phone) are the vendors’ own agents. A third-party agent gets in by forwarding, SIP device registration, an SBC trunk, a contact centre path or, on Zoom Phone, a Marketplace-listed virtual agent. On Zoom, forwarding may not pass the caller’s number.
If you are asking “how do I put my own AI voice agent on RingCentral?” or “can I connect a third-party AI agent to Zoom Phone?”, the answer depends on which door you use, and each door has a limitation its vendor documents. Every vendor fact below comes from RingCentral’s or Zoom’s own support articles, developer guides and SDK, read on 30 September 2026. The entities you will meet: RingEX, RingCentral AI Receptionist (AIR), RingCX, the Existing Phone device, Bring Your Own Carrier (BYOC), Zoom Phone, Zoom Virtual Agent (ZVA), Auto Receptionist, BYOC-P, BYOP-P, Provider Exchange, Zoom Contact Center and session border controllers (SBCs).
Can I put a third-party AI voice agent on RingCentral or Zoom Phone?
Yes. Apart from the vendors’ own agents, most of the doors are general telephony features that an AI platform can use: forwarding, SIP devices and SBC trunks. Here are the five routes this page compares:
- The vendor’s own AI agent. RingCentral AIR or Zoom Virtual Agent Receptionist. This is not a third-party agent, but it is the baseline every other route competes with.
- Forward calls to the agent’s phone number. Your third-party agent has its own number, and a RingCentral call rule or Zoom auto receptionist sends calls there.
- Register the agent as a SIP device on an extension. RingCentral calls this an Existing Phone. Zoom calls it a generic device.
- Trunk through a session border controller. This is RingCentral BYOC, or Zoom BYOC-P and BYOP-P. These features are built for carriers and PBXs, and an AI agent can sit behind your own SBC.
- The contact centre and marketplace paths. RingCX’s Bot and IVA SIP integration, Zoom Contact Center’s third-party voice bot framework, and the third-party agents listed on Zoom Phone’s Virtual Agents page.
The sentence to keep: on RingCentral and Zoom Phone, a third-party AI voice agent is a number you forward to, a SIP device you register, or a SIP peer behind your own SBC (and, on Zoom Phone, a Marketplace-listed virtual agent reached through a Zoom-provided integration number), and each carries a different documented limitation.
This mirrors our guide to putting an AI voice agent on Microsoft Teams Phone, but the answer differs: Microsoft publishes an integration for certified agents. RingCentral publishes its own agent plus general-purpose SIP and forwarding features. Zoom does the same, and Zoom Phone also lists third-party virtual agents from Zoom App Marketplace Connections, although the Zoom support article we read covers managing those listings and says only that a Zoom-provided integration number routes calls to them, not what caller data they receive. Our setup guides for an AI voice agent on 3CX, FreePBX or Asterisk and an AI voice agent on Genesys or Amazon Connect answer the same question for other phone systems.
RingCentral: the five routes and each one’s documented limitation
Every cell comes from a RingCentral page named in the source table at the end. The last column is the sentence on RingCentral’s own page that most weakens that route.
| Route | How RingCentral documents it | What you need | RingCentral’s own limitation |
|---|---|---|---|
| 1. AIR (RingCentral’s agent) | AIR is generated from your website, Google Business Profile or an existing IVR, answers questions, and transfers callers “based on verbal cues” | AIR add-on to RingEX from US$39 a month with 100 minutes, or standalone from US$49 | Overage is US$0.50 a minute, billed in 30-second increments, and test calls count towards monthly minutes. Available in the US, Canada, Australia, the UK and Europe |
| 2. Forward to the agent’s number | Call rules, then Forward all calls, then Number, on an extension, in the app or Admin Portal | One extension with a forwarding rule, and the AI vendor’s phone number | A “special number” added to caller ID can cause “failure to forward the call completely” if the carrier doesn’t support it. Forwarded phones can also hear a business-call announcement unless it is set to Never |
| 3. Register as an Existing Phone | Admin Portal: Add Device, then Other Phones, then Existing Phone, then Set up manually using SIP | An Existing Phone device with a number and emergency response location, plus SIP domain, outbound proxy, username, password and authorisation ID. The Softphone SDK uses the TLS proxy; RingCentral’s manual-provisioning article asks whether the device will use secure voice transport, and its steps answer No | The Softphone SDK’s README lists five limitations. Only the most recent registration receives inbound calls, inbound invites carry no telephony session or party IDs, and custom caller ID is not supported |
| 4. BYOC through your gateway | “For multinational customers”: your local carrier connects to RingEX through a gateway you buy and own | Your account manager must turn on BYOC and add the gateways and carrier numbers | “Emergency calling may not be available with the BYOC solution in all countries”, and RingCentral takes no responsibility for the performance, security or availability of the local carrier service or gateway |
| 5. RingCX Bot and IVA SIP | RingCX places a SIP call to your IVA’s SIP URI from a Workflow Studio node, over UDP, TCP or TLS | A RingCX contact centre account, not just RingEX | “There is no authentication mechanism per se”. It relies on IP allowlisting, and “potential issues with the size of the custom data” is its listed limitation |
Two more RingCentral facts. First, the Call Supervise API can stream a live call’s audio to an app, but the developer guide says “currently, the only supported mode is Listen”: good for transcription or agent assist, not for an AI that has to speak. Second, AIR’s release notes move RingCentral’s own agent the other way, onto “cloud, on-premises, or SIP phone systems” (AIR Everywhere, August 2025) and, from October 2025, “direct SIP integration with existing PBX systems”.
Zoom Phone: the five routes and each one’s documented limitation
| Route | How Zoom documents it | What you need | Zoom’s own limitation |
|---|---|---|---|
| 1. ZVA Receptionist (Zoom’s agent) | An “AI-powered auto receptionist” that routes to call queues, shared lines or people, books through Zoom Scheduler and answers from a knowledge base | A Zoom Phone licence and a Zoom Virtual Agent for voice licence. Booking also needs a Zoom Scheduler licence. From US$0.25 a minute billed annually, plus the cost of Zoom Phone | Cancelling or rescheduling appointments is not supported during calls. For CRM integration, the FAQ says to “contact Zoom Support for paid implementation assistance” |
| 2. Forward to the agent’s number | Auto receptionist routing option “Phone Number: Route to an external phone number”, or a user’s call handling rule | A direct number on the auto receptionist. For user forwarding, the user needs a DID | “Calls routed to an external phone number will be billed at the plan rate”. On external forwards, the receiving party “will see your caller ID name and number”, not the caller’s. The original number goes to carriers “as a best effort” |
| 3. Register as a generic SIP device | Phones & Devices: add a device with device type Other, assign it to a user, then Provision to see the SIP account details | Zoom Support must enable the Generic SIP feature on the account. The form asks for a MAC address | “You must manually enable TLS 1.2 for SIP registration and SRTP”, and you accept the security risk before the SIP details are shown |
| 4. BYOC-P or BYOP-P through your SBC | You connect your own SBC to Zoom Phone for your carrier (BYOC-P) or your PBX (BYOP-P, Zoom Phone only) | A public trusted certificate, TLS 1.2 and SRTP, SIP Early Offer, a route group and a SIP group | “Only TLS is supported”. SIP REFER transfer support applies to Zoom Phone “but not to Zoom Phone BYOP-P calls”, and route groups “may take up to 48 hours” |
| 5. Contact centre and marketplace | Zoom Contact Center’s third-party voice bot framework (Marketplace app, Actions and Triggers, SIP trunk). Zoom Phone’s Virtual Agents page also lists third-party agents from Marketplace Connections | For Zoom Contact Center: an SBC trunk built with the Zoom ISV team. For Zoom Phone: the Zoom-provided “integration number”, configured in the third-party system. The same article lists a Zoom Virtual Agent for voice licence among the requirements for managing Virtual Agents | The voice bot framework is for Zoom Contact Center, and its trunk goes through 3 phases with Zoom: discovery, staging, then production. The Zoom Phone article covers managing the listing, and routing breaks if the integration number changes on one side only |
Zoom’s Realtime Media Streams (RTMS), the feed that gives apps live call audio, lists Zoom Contact Center, Zoom Meetings and the Zoom Video SDK on its overview page. Zoom Phone was not on that list as at 30 September 2026. So do not plan around a Zoom-supplied live audio feed from Phone calls. The call itself has to reach the agent.
What you need before the first test call
This is the minimum bill of materials for the three general-purpose routes a third-party agent can use on either platform (route 5 depends on a contact centre product or, on Zoom Phone, a Marketplace listing), with each line taken from the vendor pages above. We built it for the smallest real deployment: one main number whose calls reach the AI first, with a way back to a person.
| Route | RingCentral minimum | Zoom Phone minimum |
|---|---|---|
| Forward to the agent’s number | 1 extension with a Forward all calls rule to the agent’s number. Incoming call information set to show the caller’s number, and the announcement set to Never | 1 auto receptionist with a direct number, routed to “Phone Number”. External minutes are billed at your plan rate |
| Register as a SIP device | 1 Existing Phone device on a user, with a number and emergency response location. SIP through a regional outbound proxy (the SDK README connects over TLS, for example sip20.ringcentral.com:5096). Codec OPUS/16000 by default, or OPUS/48000/2 or PCMU/8000 | 1 generic device (type Other) after Zoom Support enables Generic SIP. TLS 1.2 and SRTP enabled by you |
| SBC trunk | BYOC turned on by your account manager, plus a customer-owned gateway and carrier numbers | 1 SBC with a publicly trusted certificate, TLS 1.2, SRTP, Early Offer, and one of Opus, G722, G711ulaw, G711alaw or G729. Plus 1 route group, 1 SIP group and a routing rule |
Zian builds autonomous AI sales agents that call leads, follow up and book meetings, work that doesn’t need to sit in front of your main number. If that is your job to solve, Apply For Partnership. Zian is in partnership-application beta.
How to set it up, step by step
The order works for either vendor: step 1 is yours, steps 2 to 4 the phone administrator’s, and 5 and 6 the AI agent owner’s.
- Day one: decide whether the caller’s number has to reach the agent. If the agent looks up the caller in a CRM, verifies identity or texts a link back, it needs the number. On Zoom, that makes plain external forwarding a risk (see the next section). On RingCentral, it means setting Incoming call information to show the caller’s number.
- Pick the entry point. On RingCentral, that is the extension whose calls go to the AI. On Zoom, it is an auto receptionist with a direct number, or a user with a DID.
- Create the route. For forwarding: RingCentral Call rules, then Forward all calls, then Number, or Zoom auto receptionist routing to Phone Number. For SIP: add an Existing Phone and copy the SIP settings, or add a generic device on Zoom after Zoom Support enables it. For an SBC: have BYOC turned on (RingCentral) or build the SBC, route group and SIP group (Zoom).
- Set the handoff destination back. Decide which number or extension the agent transfers to when it needs a person. On a SIP device, that is a transfer from the device. On forwarding, it is usually a call back into your main number or a direct number.
- Configure the agent’s side. Enter the SIP credentials or the forwarding number in the AI platform. On RingCentral, check which transport the platform uses (the manual-provisioning article asks about secure voice transport and its steps answer No, while the Softphone SDK connects over TLS) to RingCentral’s proxy. On Zoom’s SBC route, check whether it supports SIP Early Offer.
- Run the two-call test below before you move the main number.
Finish state: a call to your main number reaches the agent, its log shows the real caller’s number, and a request for a person lands on a named human with the call still up.
We have not run these steps against a live RingCentral or Zoom tenant. They are the vendors’ documented steps, cited as written, not a tested runbook.
Why does my AI voice agent not see the caller’s number on Zoom Phone?
This is the most useful sentence in Zoom’s caller ID FAQ, and it cuts straight against the easiest route: “When you transfer or forward calls to an external number, the receiving party will see your caller ID name and number. They will not see the caller ID of the party that is being transferred or forwarded.” The note directly under it softens this: “The original calling number is sent as a best effort to our carriers; however, the actual presentation of the caller ID name may vary depending on the underlying carrier on the receiving end.”
For a third-party AI agent reached by forwarding, the “receiving party” is the agent. By Zoom’s main sentence, calls can arrive looking as if they came from your own business number. By its note, whether the real number gets through depends on the carriers in the path. If it does not, the practical costs are:
- the agent cannot look the caller up in your CRM by phone number;
- it cannot text a confirmation or a link back to the caller without asking for their number;
- callback, spam screening and repeat-caller logic all see one number.
Zoom’s SBC route has a documented way around this. The BYOC-P configuration guide offers a per-SBC option to “include original calling number within the P-Asserted-Identity (PAI) header for forwarded calls”, and another to include diversion headers. So on Zoom, the SBC route is the one to use when the caller’s number matters. Its catch: Zoom’s REFER support does not apply to BYOP-P calls, so an agent behind a BYOP-P trunk cannot hand a call back with a REFER.
RingCentral lets you choose what forwarded calls show on non-RingCentral phones. Its Incoming call information setting lets the extension choose “Incoming caller ID: Shows the caller’s phone number” or “Dialed number”, and choose where that applies. The same page warns about the other trap on this route. A business-call announcement can play on personal and mobile phones, and RingCentral’s own note on the Never option is “Select this option if calls are forwarded to an answering service”. An AI agent is an answering service for this purpose. If you leave the announcement on, the first thing your agent hears is RingCentral talking. The Never option is listed for Direct calls only: for Call queue calls the page offers only personal and mobile phones or Always, so keep the extension that forwards to the agent out of call queues.
If you need the caller’s identity inside the agent, our walkthrough on getting the caller’s number into your AI voice agent through SIP headers covers the PAI and diversion headers that the SBC route can carry.
The two-call test
We call this the two-call test. Run it on a spare number before you move the main line to any route.
- Call one: identity. Ring the entry number from a mobile whose number you know. Check the agent’s call log. If it shows your business number instead of the mobile, you have hit Zoom’s documented forwarding behaviour, or a RingCentral extension set to show the Dialed number. The agent cannot identify callers by number on this route.
- Call two: handoff. Ring again and ask the agent for a person. The call should land on a human with the caller still connected. On a RingCentral Existing Phone, remember the SDK’s note on declined calls. “RingCentral may already have answered the caller-facing leg before your device was presented the call”, so a decline can leave the caller in an answered call that RingCentral then routes elsewhere, “for example toward voicemail”. On a Zoom BYOP-P trunk, test the transfer method your agent uses, because REFER is not supported there.
If call one fails and the agent needs the caller’s number, change route rather than working around it in the agent. Our breakdown of why AI voice agent transfers to a human fail covers call-two failures that apply on any phone system.
Registering the agent as a SIP device: what RingCentral’s own SDK says
One direct way to put a third-party agent “on an extension” in RingCentral is to give it the credentials of an Existing Phone. RingCentral’s GitHub organisation publishes a headless Node.js softphone SDK, ringcentral-softphone (latest release 1.3.9 on npm as at 30 September 2026, published 21 May 2026). It “supports inbound and outbound calls, DTMF, audio streaming, transfer, hold, and unhold without a browser”. It is RingCentral’s own published code for this route. Its README also lists the limitations, and three of them matter for an AI agent:
- “Only the most recent registration receives inbound calls when credentials are shared by several instances.” Two copies of your agent on one Existing Phone do not share the calls. The newest one takes them.
- “Inbound invites do not provide RingCentral telephony session or party IDs.” To use the Call Control REST API on a call your agent answered, you have to find the session some other way.
- “Selecting a custom caller ID is not supported.”
The same README notes that “a device shown as the RingCentral desktop or mobile app is not an Existing Phone device”, so you cannot borrow a user’s app login for this.
RingCentral’s ideas board shows what can happen when a hosted AI platform tries to connect. A customer request, “Enable SIP Trunking Support for Third-Party AI Platforms Like ElevenLabs”, reports “TLS handshake failures due to certificate validation issues” and describes RingCentral’s SIP endpoints as “designed for device registration only, not for SIP trunking”. That is a customer’s wording on RingCentral’s forum, not a RingCentral statement. As at 30 September 2026 it showed status New and 18 votes (posted 23 July 2025). So ask your AI vendor whether it registers as a SIP device (a client) or expects a SIP trunk (a peer).
What if my AI agent needs a SIP trunk, not a device?
Then use the SBC route, with different fine print on each platform.
On Zoom Phone, BYOP-P is the closest documented fit. It “enables integration with an on-premises PBX through the configured SBC” and “allows extension dialing between Zoom and the on-premises PBX”. An AI platform behind your SBC can be reached the way a PBX would be. That is our inference: Zoom documents BYOP-P for PBXs, not for AI agents. Zoom maintains a list of certified SBC vendors and models. It requires a certificate from one of its approved certificate authorities, requires SIP Early Offer on INVITEs sent to Zoom, and supports five codecs: Opus, G722, G711ulaw, G711alaw and G729. Provider Exchange is the no-hardware alternative, but it connects carriers listed in the Zoom portal, not arbitrary SIP endpoints.
On RingCentral, BYOC is described as a service “for multinational customers” who keep a local carrier. The gateway is purchased and owned by the customer, and RingCentral “has no liability or responsibility” for the performance, security or availability of the local carrier service or gateway. If you already run a certified SBC for BYOC, routing the main number to an AI platform before RingEX is an SBC configuration job. The BYOC pages we read describe carrier connections, not AI routing, so plan and test it as your own design.
If you run a contact centre rather than a business phone system, the doors are wider: RingCX has a named Bot and IVA SIP integration that passes session context to the bot and gets intent back through SIP INFO, and Zoom Contact Center has a third-party voice bot framework built with Zoom’s ISV team.
Which route should I use? A decision table
| Your situation | Route that usually fits | Why, from the vendor’s page |
|---|---|---|
| You want an AI front desk, and it does not have to be a specific third-party agent | 1 (AIR or ZVA Receptionist) | Configured in the vendor’s own admin portal with vendor support. You accept its limits: per-minute billing, and on ZVA no appointment changes during calls |
| RingCentral, third-party agent, caller number needed | 2 (forward), with Incoming caller ID shown and the announcement set to Never | RingCentral’s Incoming call information setting can show the caller’s number on forwarded phones. It is the fastest route to test |
| Zoom Phone, third-party agent, caller number not needed | 2 (forward from an auto receptionist), or 5 if your AI vendor is listed in Zoom App Marketplace Connections | Route 2 needs only a direct number on the auto receptionist, and minutes are billed at your plan rate. Route 5 needs the Zoom-provided integration number entered in your AI vendor’s system |
| Zoom Phone, third-party agent, caller number needed | 4 (BYOC-P or BYOP-P with the PAI option), or 3 if Zoom Support enables Generic SIP, or 5 if your AI vendor is listed in Zoom App Marketplace Connections (test caller ID with call one: Zoom’s article documents managing the listing, not what it passes) | Zoom’s external forwarding shows your caller ID, and passes the caller’s number to carriers only as a best effort. Route 3 is our inference: a registered device takes the call as the user’s own phone, not as an external forward, so confirm it with call one of the two-call test |
| You build your own agent in code and want it on a RingCentral extension | 3 (Existing Phone plus the Softphone SDK) | RingCentral publishes the SDK. Plan around the one-registration-receives-calls limit |
| Your AI platform only speaks SIP trunking | 4 (SBC), or 5 if you run RingCX or Zoom Contact Center | RingCentral documents Existing Phone SIP settings for third-party IP phones, not trunks. BYOC and BYOP-P are built for carriers and PBXs |
| The AI only makes outbound sales calls | None of the five | An outbound agent does not need to intercept your inbound number at all |
The honest DIY cost
Routes 2 to 4 are DIY. What they take to run:
- Two sets of skills. RingCentral or Zoom phone administration (extensions, call rules, auto receptionists, devices) and SIP on the AI side (TLS certificates, codecs, SRTP). The SBC route adds a third: running an SBC to Zoom’s certified-vendor list or RingCentral’s BYOC gateway terms.
- Two support queues, and a gap between them. RingCentral and Zoom support their own agents. On routes 2 to 4, the AI agent is your AI vendor’s problem, and the network between them is yours. On BYOC, RingCentral’s service description says it “has no liability or responsibility” for the performance, security or availability of the local carrier service or gateway.
- Minutes on both sides. Zoom bills external forwards at the plan rate, and your AI vendor bills its own minutes. For comparison, AIR overage is US$0.50 a minute and ZVA Receptionist on Zoom Phone starts at US$0.25 a minute billed annually.
- Provisioning waits. Zoom’s Generic SIP needs a support ticket, and BYOC-P route groups can take up to 48 hours. RingCentral BYOC goes through your account manager.
For an inbound front desk, the vendor’s own agent usually needs the least plumbing. For outbound work (calling leads, following up and booking meetings), none of this plumbing applies. Zian’s agents do that work over phone, SMS, email and WhatsApp in 30+ languages, with published integrations for HubSpot, Salesforce, HighLevel and Zapier plus an API. Zian does not publish a RingCentral or Zoom Phone integration. Our comparison of an AI receptionist versus an autonomous sales agent sets out where the line between the two jobs sits.
Frequently asked questions
Can I use my own AI voice agent with RingCentral instead of AIR?
Yes. The two most direct documented doors are forwarding an extension’s calls to the agent’s number, or registering the agent as an Existing Phone SIP device on a user; BYOC and RingCX’s IVA SIP integration are heavier options. RingCentral publishes a headless softphone SDK for the second route, and its README says only the most recent registration receives inbound calls. See RingCentral’s SIP settings for manual provisioning.
Can I connect a third-party AI agent to Zoom Phone?
Yes. Zoom documents routing an auto receptionist to an external phone number, a generic SIP device that Zoom Support must enable, and BYOC-P or BYOP-P through your own SBC. Zoom Phone’s Virtual Agents page also lists third-party agents from Zoom App Marketplace Connections, each with a Zoom-provided integration number.
Why does my AI agent see my business number instead of the caller on Zoom?
Zoom’s caller ID FAQ says that when you transfer or forward calls to an external number, the receiving party sees your caller ID name and number, not the caller’s. Zoom adds that the original calling number is sent to carriers as a best effort, and that caller ID presentation can vary by carrier. Zoom’s BYOC-P SBC settings include an option to put the original calling number in the P-Asserted-Identity header for forwarded calls.
How much do RingCentral AIR and Zoom Virtual Agent Receptionist cost?
RingCentral lists AIR as a RingEX add-on from US$39 a month or standalone from US$49, each with 100 minutes and US$0.50 a minute overage. Zoom lists ZVA Receptionist with Zoom Phone from US$0.25 a minute billed annually, plus the cost of Zoom Phone. Standalone ZVA Receptionist was announced from US$29.99 a month for 100 minutes.
Does Zoom Phone support SIP trunking to an AI platform?
Zoom documents BYOC-P for carriers and BYOP-P for PBXs through a customer SBC, over TLS only, with SIP Early Offer and a certified SBC list. Zoom documents BYOP-P for PBXs, not AI platforms, so an AI platform behind the SBC is your own design. SIP REFER transfers are not supported on BYOP-P calls, and route groups can take up to 48 hours.
Is RingCentral AIR available in Australia?
Yes. RingCentral’s AIR setup article says AIR is available in the US, Canada, Australia, the UK and Europe, and that some features vary by country. AIR’s August 2025 release notes added English for Australia and the UK as primary languages.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| AIR from US$39 (RingEX add-on) or US$49 (standalone), 100 minutes, US$0.50 per minute overage, 30-second increments | RingCentral | AI Receptionist plans and pricing | 30 September 2026 |
| AIR available in 5 regions (US, Canada, Australia, UK, Europe); test calls count towards minutes; connection to a number or extension required | RingCentral Support | Setting up your AI Receptionist | 30 September 2026 |
| AIR Everywhere (August 2025); Australian English (August 2025); external PBX SIP integration (October 2025) | RingCentral Support | AIR release notes (August 2025 and October 2025 pages) | 30 September 2026 |
| Forward all calls to an external number | RingCentral Support | Forwarding calls | 30 September 2026 |
| Special number can cause failure to forward | RingCentral Support | Why are my calls not forwarding | 30 September 2026 |
| Incoming caller ID vs Dialed number; announcement Never for answering services | RingCentral Support | Set incoming call information display | 30 September 2026 |
| Existing Phone manual SIP provisioning steps | RingCentral Support | Getting the SIP settings for manual provisioning | 30 September 2026 |
| Softphone SDK: 5 listed limitations; default codec OPUS/16000; proxy example sip20.ringcentral.com:5096 | RingCentral (GitHub) | ringcentral-softphone-ts README | 30 September 2026 |
| Softphone SDK latest release 1.3.9, published 21 May 2026 | npm registry (RingCentral package) | ringcentral-softphone | 30 September 2026 |
| Ideas board request: 18 votes, status New, posted 23 July 2025 | RingCentral Ideas (customer-submitted) | Enable SIP Trunking Support for Third-Party AI Platforms | 30 September 2026 |
| BYOC for multinational customers; customer-owned gateway; emergency calling caveat | RingCentral | BYOC Service Description | 30 September 2026 |
| BYOC turned on by account manager | RingCentral Support | Adding a user phone using your own carrier | 30 September 2026 |
| RingCX IVA over SIP; no authentication mechanism; custom data size limitation | RingCentral Developers | Bot and IVA SIP integration | 30 September 2026 |
| Supervise API: only supported mode is Listen | RingCentral Developers | Call supervision, monitoring and streaming | 30 September 2026 |
| ZVA with Zoom Phone requirements (Zoom Phone licence, ZVA for voice licence) | Zoom Support | Integrating Zoom Virtual Agent with Zoom Phone | 30 September 2026 |
| ZVA: routes to external numbers; no cancel or reschedule during calls; paid implementation for CRM; Zoom Scheduler licence needed for booking | Zoom Support | ZVA Receptionist FAQ | 30 September 2026 |
| ZVA Receptionist with Zoom Phone from US$0.25 per minute billed annually, plus Zoom Phone | Zoom | AI Receptionist for Zoom Phone | 30 September 2026 |
| Standalone ZVA Receptionist from US$29.99 per month per 100 minutes (US$24.99 annual), announced 9 July 2026 | Zoom | Zoom news release | 30 September 2026 |
| Third-party agents listed from Marketplace Connections; integration number routes calls; Zoom Virtual Agent for voice licence among the requirements | Zoom Support | Managing Virtual Agents in Zoom Phone | 30 September 2026 |
| Auto receptionist routing to an external number: direct number required, billed at plan rate | Zoom Support | Changing auto receptionist settings | 30 September 2026 |
| Users without a DID cannot forward externally | Zoom Support | Zoom call handling settings | 30 September 2026 |
| External forwards show your caller ID, not the caller’s; original number sent to carriers as a best effort | Zoom Support | Caller ID FAQ | 30 September 2026 |
| Generic SIP needs Zoom Support; TLS 1.2 and SRTP enabled manually | Zoom Support | Managing phones and devices | 30 September 2026 |
| BYOC-P and BYOP-P: TLS only; REFER not on BYOP-P calls; route groups up to 48 hours; PAI option; BYOP-P setting description (PBX integration and extension dialling through the SBC) | Zoom Support | BYOC-P or BYOP-P configuration guide | 30 September 2026 |
| Certified SBC list; SIP Early Offer; 5 codecs | Zoom Support | BYOC-P or BYOP-P infrastructure requirements | 30 September 2026 |
| BYOP-P for PBX through an SBC; deployment options | Zoom Support | BYOC-P or BYOP-P deployment and connectivity options | 30 September 2026 |
| Provider Exchange connects listed carriers | Zoom Support | Setting up Phone provider exchange | 30 September 2026 |
| Zoom Contact Center third-party voice bot trunk: 3 phases with the Zoom ISV team | Zoom Developers | Configure the SIP Trunk and SBC Network | 30 September 2026 |
| RTMS available for Contact Center, Meetings and Video SDK | Zoom Developers | Realtime Media Streams | 30 September 2026 |
Want an AI agent working your outbound pipeline rather than your switchboard? Zian is in partnership-application beta. Apply For Partnership.