What this page covers
An AI voice agent connects to RingCentral the same way an outside phone number does: a RingCentral routing setting sends selected calls to it. On a user extension, a work-hours, after-hours or custom call handling rule can forward to an external number. On a call queue, the no-answer, maximum-wait and full-queue actions can each do the same. The main number keeps its IVR menu, and your numbers, desk phones and RingCentral app stay as they are. A practice usually starts with after-hours calls or queue overflow.
How Does an AI Voice Agent Connect to RingCentral?
Through routing settings RingCentral already has. The agent gets its own phone number, and RingCentral sends the calls you choose to that number. Three places in RingCentral can do it, and the deployment uses whichever matches the calls you want to hand over.
- User extension call handling rules. Each extension can keep separate work-hours, after-hours and custom rules, and a forwarding target can be an external phone number. A dedicated extension for refills or Spanish-speaking callers can forward straight to the agent.
- Call queue actions. A queue has settings for when no one answers, when the maximum wait time is reached, and when the queue is full. Each one can forward the caller to an external number, so front-desk overflow reaches the agent instead of voicemail.
- Main number routing. Company call handling sends the main number to an IVR menu, a call queue or a user, with separate business-hours and after-hours settings. Pointing the after-hours route at a forwarding extension or queue sends nights and weekends to the agent.
RingCentral documents these options in its developer guides for user call forwarding targets and call queue call handling. Its support article on company call handling covers the main number. At higher volume, the connection can run over SIP instead of a forward, but a forwarding rule is enough for a pilot.
Get an outside read on your RingCentral 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.
Which Calls Does the Agent Take First?
The ones the audit shows are frequent and follow clear rules. Flexbone starts with a complimentary audit of a sample of your calls, sorted by reason. In medical practices, these call types often come out near the top.
- Appointment changes, which one group told us were its largest reason for inbound calls. The agent books, reschedules and cancels against your schedule.
- Refill requests. The agent captures the medication, pharmacy and patient details and sends the request to your clinical staff queue. It makes no clinical decision.
- Insurance questions. The agent runs an eligibility check and reads back coverage details, and it routes billing disputes to staff.
- After-hours calls, answered in place of voicemail, with urgent calls escalated by your on-call rules. The after-hours answering service page covers that path.
- Spanish-speaking callers, handled in Spanish on the same line or on a dedicated Spanish number. More on bilingual answering.
What Happens When a Caller Needs a Person?
The agent transfers the call to a RingCentral destination you choose, such as a user's direct number or a call queue's number. Before it connects the caller, it tells the staff member who is calling and what has been checked. The transcript is saved with the call. Clinical questions, billing disputes and requests outside the rules built from your SOPs go to a person this way.
For a forwarded call, the transfer is a PSTN call to that number. Over a SIP connection, the agent can use a SIP REFER so the call leaves the agent's path. In both cases the caller does not repeat the request, and your staff see the call arrive like any other RingCentral call.
Does This Change Our RingCentral Setup?
Only the routing setting that hands calls to the agent changes. Your numbers stay on your RingCentral account, nothing is ported, and desk phones and the RingCentral app work as before. The IVR menu, other queues and staff extensions keep their rules. Undoing the change means pointing that rule back at its old target.
Before go-live, your RingCentral administrator and the Flexbone engineer agree on three settings. The first is the rule or queue action that forwards to the agent. The second is the hours each rule applies. The third is the list of direct numbers the agent can transfer to. A round of test calls then shows which caller ID the agent receives, since it uses that number to find the patient record.
How Do Results Get Into Our EHR?
RingCentral stays the phone layer, and the EHR stays the record. Where the connection is set up, the agent writes appointments, messages and call notes to the chart. Flexbone works in eClinicalWorks, athenahealth and Tebra. It uses a vendor API where one exists, and a browser automation in the screens staff use where it does not. Until a connection is in place, the agent sends a structured message to a staff queue instead.
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.