Integrating RingCentral Fax with Your ABA Intake Workflow

RingCentral is the fax provider most ABA centers already have, often because it also runs their phone system. That makes it the natural first integration for intake, and it is TargetFlo's primary live fax integration today. Connect the two and an inbound referral fax stops being a PDF in someone's email and becomes a referral card with an owner in the same business day.

This post walks through exactly how that works: how RingCentral delivers the fax, how TargetFlo captures it, how the document becomes a card in the intake pipeline, and how SMS on the same RingCentral number closes the loop with the family.

What is the RingCentral fax integration in TargetFlo?

The RingCentral fax integration connects a center's RingCentral account to TargetFlo's fax inbox so inbound faxes are captured automatically, read by OCR and AI extraction, linked to client records, and turned into referral cards without manual downloading or retyping. It uses RingCentral's inbound message webhooks for real-time capture, a periodic message sync for completeness, and RingCentral SMS for outbound guardian communication from the same number families already recognize.

How the integration works, step by step

Step 1 and 2: Inbound webhooks

When a fax arrives on a RingCentral number, RingCentral can send an event notification to a registered endpoint. TargetFlo subscribes to inbound fax message events for the numbers you choose. The webhook carries the message identifier, receiving number, sender number, and page count, which is enough for TargetFlo to fetch the document and place it in the queue within moments of arrival.

Because the receiving number is included, multi-location centers see each fax tagged to the right location automatically. A fax to the Charlotte number lands in Charlotte's queue; the organization view shows both.

Step 3 and 4: Fetch and sync

TargetFlo retrieves the fax pages and stores them as a document attached to the queue item. Webhooks are fast but not perfect, so TargetFlo also runs a periodic sync that lists recent fax messages in RingCentral and captures anything not already present. The two mechanisms together mean real-time capture in the normal case and no lost referrals in the abnormal case.

Step 5: OCR and AI extraction

Once the document is in the queue, TargetFlo runs OCR and Gemini-powered extraction to pull structured fields: child's name and date of birth, guardian name and phone, referring provider and NPI, diagnosis code, and insurance payer and member ID. Extracted values appear beside the fax preview so the coordinator can confirm or correct them. See AI-powered OCR for healthcare fax for what extraction handles well and where a human still matters.

Step 6: Triage

The coordinator classifies the fax. If it is a document for a family already in the pipeline, they link it to that client and the fax appears in the client's record. If it is a new referral, they confirm the extracted fields and proceed to card creation. If it is a pharmacy advertisement, they archive it. Untriaged faxes older than a business day appear in the daily review.

Step 7: How a fax becomes a referral card

This is the point of the integration. Confirmed fields become a client record in the Client & Family Hub and a referral card at the New Intake stage. The card is assigned to a coordinator, carries a follow-up date, records the referral source as fax with the referring provider's details, and has the original fax attached as its first document.

From here the referral moves through the 9-stage pipeline: Insurance, where a 270/271 eligibility check runs on the extracted member details; Pending Documents; Diagnostics; FBA; POC; Pending Authorization; and Enrolled. The 9-stage ABA intake pipeline guide covers each stage.

Step 8: SMS follow-up on the same number

Guardians recognize the center's phone number, and RingCentral lets the fax number and SMS number be the same. TargetFlo's communications tools send SMS through RingCentral with a PHI guard that blocks messages containing protected details, so a coordinator can text "We received a referral for your family and would love to schedule a call. Reply with a good time." without exposing diagnosis or insurance information over text.

What you need to set it up

• A RingCentral account with fax-enabled numbers for each location.
• API credentials for TargetFlo to subscribe to message events and fetch documents.
• A decision on which numbers route to which TargetFlo location.
• SMS-enabled numbers if you want outbound texting from the same line.

Setup is typically completed in a working session, after which coordinators test with several real referral faxes to see the full flow.

What the integration does not do

TargetFlo does not send outbound faxes to payers for authorization or claims today. Claims submission and the authorization management UI are on the roadmap, and when they arrive, outbound fax through RingCentral is a natural extension. Today the integration is focused on inbound capture, extraction, linking, and SMS, which is where intake leakage actually happens.

Other providers

RingCentral is the primary live integration, but TargetFlo positions flexible connectivity for centers on eFax, SRFax, Concord, OpenText RightFax, and Documo or iFax. Inbound documents from those providers can be routed into the same triage inbox, where extraction, linking, and card creation work identically. If you are still choosing, our guide to choosing a cloud fax provider compares all six, and the fax integrations page lists current options.

The result

Centers running the RingCentral integration measure the same thing: time from fax arrival to referral card. Before, it was measured in days and depended on who checked the inbox. After, it is measured in hours and depends on nothing but the coordinator's triage queue. That is the difference between a fax machine and an intake front door.