What this page covers
On Nextiva, an AI voice agent is an outside number your call flow or PBX already knows how to reach. In Nextiva's hosted call flows, a Transfer Out node sends a call to a 10-digit number. A Schedules node can limit that to closed hours. With Nextiva SIP Trunking, routing lives in your own PBX, which forwards the chosen calls the same way. In both setups, your numbers, phones and the rest of the call flow stay where they are.
How Does an AI Voice Agent Connect to Nextiva?
It depends on which Nextiva service you run. Nextiva sells a hosted voice service, where routing is built as call flows in the Nextiva portal. It also sells SIP Trunking, a non-hosted service that connects your own PBX to Nextiva. The agent fits both.
In a hosted call flow, the nodes Nextiva lists are Schedules, Phone Menu, Users & Teams, Transfer Out, Voicemail and Call Flow. Transfer Out is a terminating node that sends the call to an outside 10-digit number or an internal extension. That makes it the node that reaches the agent. A Schedules node splits the flow into open and closed branches, with holidays taking priority over regular hours. Its closed branch can end in Transfer Out to the agent. A Phone Menu option can do the same for one call type, such as appointments. Nextiva's call flow guide covers each node.
For calls to one user or team, Call Forwarding Selective forwards by rule and schedule, and Nextiva describes it for after-hours and holiday routing. It uses a first-match policy, and Nextiva describes it as the highest-priority form of forwarding. On a user, it forwards direct calls only, not calls distributed from a call center or call group. Queue traffic is therefore routed in the call flow instead.
With Nextiva SIP Trunking, your PBX keeps its own features and routing, and the agent connects there. A PBX route or menu option forwards chosen calls to the agent's number, or a separate SIP connection carries them. Nextiva counts one trunk line per simultaneous call. A call the PBX forwards back out over the same trunk can hold two lines while it is connected. Size the trunk count for that, or connect the agent to the PBX over its own SIP route.
Get an outside read on your Nextiva calls workflow
In 30 minutes we map your current volume, the payers and systems involved, where staff time goes, and the highest-ROI calls and follow-ups Flexbone can take off your team first, scoped to the work you actually run.
How Do We Change a Live Nextiva Call Flow Safely?
Plan the change, because Nextiva requires some edits to happen on a deactivated flow. Adding or removing nodes, or adding or removing Phone Menu options, needs the call flow deactivated first. While it is deactivated, the numbers tied to it return a Not In Service message. Nextiva recommends duplicating a call flow before changing it, so the old version can be restored quickly.
In practice, the agent path is added during a quiet window, such as after the office closes, with the duplicate ready. Nextiva also requires each path to end in a terminating node with no loops. Transfer Out is a terminating node, so the agent path is complete on its own. Later adjustments, such as a new target number on an existing Transfer Out node, are node settings rather than new nodes.
Which Calls Does the Agent Take First?
Calls that are frequent, follow clear rules, and are easy to separate in a call flow. On Nextiva, a dedicated number gives the cleanest split. A refill line or a Spanish line gets its own short call flow that ends in Transfer Out to the agent. The main number keeps its Phone Menu until transcripts show the agent handles its call type.
In medical practices, the common first call types are appointment changes, refill requests, insurance and balance questions, and after-hours calls. The agent captures refill details and sends them to the clinical staff queue, and it makes no clinical decision. It answers coverage questions after an eligibility check. It handles calls in English and Spanish, which suits a dedicated Spanish line.
What Happens When a Caller Needs a Person?
The agent transfers the caller to a Nextiva number you choose, such as a user's direct number or a team's number. Before connecting, it tells the staff member who is calling and what has been checked, and it saves the transcript with the call. On a SIP Trunking setup with the agent connected over SIP, the transfer can go back to the PBX as a SIP REFER. The PBX then moves the call to the extension.
When the agent and staff share forwarding schedules, rule order matters, because Call Forwarding Selective applies the first rule that matches. Nextiva suggests numbering rule names, such as 01 Holiday and 02 After Hours, so they sort in the right order. A Do Not Forward rule overrides any other forwarding on that user, which suits a line that has to ring a person.
How Do Results Get Into Our EHR?
Nextiva routes the call, and the result is written where your staff work. With an EHR connection in place, the agent records the appointment, refill request or call note in the chart. Flexbone works in eClinicalWorks, athenahealth and Tebra, through a vendor API where one exists and a browser automation where it does not. Without a connection yet, the agent sends a structured message to a staff queue.
How Does a Flexbone Deployment Work?
Every deployment starts from the work as your team does it today, not from a product demo. The steps below are the same whether the first agent answers phones, checks eligibility, or files incoming documents.
- Audit first, then automate. We listen to a sample of your calls and read the work queues, then agree with your team on which work to automate first. The audit is complimentary.
- Forward-deployed engineers map your SOPs. An engineer sits with the staff who do the work and turns your written and unwritten rules into agent logic.
- Agents act on your rules, and exceptions go to a person. Each step follows logic built from your SOPs. A case outside those rules, or one the agent is not confident about, goes to your team with the context attached.
- Every action leaves a record. A check in a web application saves a screenshot, a call saves a transcript, and results are written back where your team already looks.
- Start with one or two agents on the systems you already run. The agents work in your EHR, practice management system, phone system, and the web applications your staff use, as they are configured today, so nothing is migrated or rebuilt.
- The same team stays after go-live. We monitor results, tune the agents as payers and workflows change, and add agents as new work is found.
The engagement model is described in more detail in forward-deployed engineering for healthcare contact centers.