External number noderoutes chosen calls to the agent, with an On timeout path back to staff
Schedule and Queuesend after-hours calls or queue overflow down the agent path
Recordings firstthe audit can start from call recordings already in GoTo Connect

An AI voice agent connects to GoTo Connect as an External number node in your dial plan. The node routes the caller to the agent's phone number. Its On timeout target decides where the call goes if the agent does not answer in time. A Schedule node can send only after-hours calls down that path. An Auto attendant option or a Queue node timeout can hand over one call type or the overflow. The rest of the dial plan, your numbers and your desk phones do not change.

How Does an AI Voice Agent Connect to GoTo Connect?

Through the dial plan. In GoTo Admin, a dial plan is a set of routing rules drawn as nodes. Connecting the agent means adding one External number node and wiring it into the flow where the chosen calls pass. GoTo's dial plan node reference describes the four nodes involved:

  • External number routes the caller to an outside phone number, here the agent's. Its Timeout and On timeout target move the call onward if the agent does not pick up. The next node can be a staff ring group.
  • Schedule routes callers to a different call flow by schedule, including custom holiday schedules. The closed branch can lead to the agent while open hours ring the front desk as before.
  • Auto attendant plays the IVR menu and routes each dialable option to its own path. One option, such as appointments, can lead to the External number node.
  • Queue holds callers for the next available staff member until its timeout. Its On timeout path can lead to the External number node, so overflow reaches the voice agent instead of voicemail.

Two External number settings need a decision during setup. Confirm call pickup asks whoever answers to press 1 to accept the call. GoTo describes it for ring steps that include a cell phone, which can send the call to its own voicemail. It is usually left off for the agent's number. GoTo also notes that the carrier decides how caller ID displays on an external number. Test calls show whether the agent receives the caller's number, which it uses to find the patient.

Complimentary Flexbone audit

Get an outside read on your GoTo Connect 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.

Book an audit →

Which Calls Does the Agent Take First?

The audit decides, and on GoTo Connect it can start from recordings you already have. Flexbone has pulled GoTo Connect call recordings for earlier Voice Room audits and sorted the calls by reason, handle time and outcome. In medical practices, the shortlist tends to include appointment changes, refill requests that go to clinical staff, and insurance and balance questions. After-hours calls and Spanish-speaking callers are often on it too.

Each call type then maps to a dial plan path. After-hours calls use the Schedule node's closed branch. A call type callers already pick from the menu uses an Auto attendant option. Front-desk overflow uses the Queue node's On timeout path. A dedicated number, such as a Spanish line, routes to its own short dial plan that starts with the External number node.

What Happens When a Caller Needs a Person?

There are two paths back to your staff. If the agent does not answer within the node's timeout, GoTo moves the call to the On timeout target. The caller reaches the front desk instead of a dead end. When the agent answers and the caller needs a person, the agent transfers the call to a GoTo line or ring group number you choose. It tells the staff member who is calling and what has been checked, and it saves the transcript with the call.

GoTo also has an HTTP notify node that posts call events to a web address as calls pass through a dial plan. GoTo lists screen pops as one use for it. That makes it the place to add one if your team wants caller details on screen when a transfer arrives.

Does This Change Our GoTo Connect Setup?

The change is one or two nodes in one dial plan. Phone numbers stay on GoTo Connect, nothing is ported, and lines, ring groups, queues and voicemail keep their settings. GoTo's Jump to dial plan node sends calls to a separate dial plan. The agent path can live in a small plan of its own. That keeps the main flow readable and the change easy to remove. At higher volume, the agent can connect over SIP instead of an outside number, but the External number node is enough for a pilot.

When the agent path comes out, the targets that pointed at it are reconnected to their old nodes. GoTo's dial plan guide warns that a target left without a destination drops the call. The edit is therefore checked before it is saved.

How Do Results Get Into Our EHR?

GoTo Connect carries the call, and the EHR holds the outcome. When a connection to the EHR is set up, the agent writes the booking, the refill request or the call note to the chart. Flexbone does this work in eClinicalWorks, athenahealth and Tebra. It uses the vendor's API where one exists and a browser automation where it does not. Before that connection exists, the agent posts 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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.