practice management

ABA Intake on Autopilot: From First Call to First Session in Days, Not Weeks

StreamABA automates ABA intake with AI insurance card scanning, secure document requests, e-signatures, insurance discovery, and a conversion checklist that ensures nothing is missed.

8 min read StreamABA Team
practice-management billing compliance

30 Days of Waiting for 4 Hours of Actual Work

Ask any intake coordinator what takes the longest in ABA intake and the answer is never “the work.” It’s the waiting. Waiting for the family to send the insurance card. Waiting for the PCP to fax the referral. Waiting for the signed ROI to come back. Waiting for the insurance company to return the VOB call.

The actual tasks — verifying benefits, collecting documents, building the client record — take a few hours total. But when each step depends on someone outside your office doing something, and your only tool is a phone call and a follow-up reminder on a sticky note, 30-45 days from first contact to first session is the norm.

That timeline costs you families. A parent who called three practices is going with the one that got back to them fastest and made the process easiest. Every day your intake sits in “Waiting on Insurance Card” is a day that family is considering alternatives.

StreamABA’s intake automation doesn’t eliminate the human steps — families still need to send documents, and payers still need to verify benefits. But it eliminates the manual overhead between those steps, tracks everything in one place, and makes sure nothing sits idle because someone forgot to follow up.

Secure Document Requests via SMS and Email

The traditional way to collect an insurance card: call the family, ask them to take a photo, hope they know how to email it, wait for a blurry JPEG to arrive, then manually enter the payer name, member ID, and group number into your system.

StreamABA replaces this with a one-click request that sends the family a secure upload link — via SMS, email, or both. They tap the link, snap photos of the front and back of the card, and submit. The images land directly on the lead’s record. No email attachments to download. No photos lost in a text thread.

Screenshot: Insurance card upload link on mobile

The same secure-link workflow handles every document type your practice collects during intake:

  • Insurance cards (front and back)
  • Release of Information (ROI)
  • Medical records
  • Referrals and prescriptions
  • Diagnosis reports
  • Consent forms
  • Restrictive procedure consent

Each request tracks its status through a full lifecycle: Not Started → Requested → Sent → Received → Verified (or Rejected, Cancelled). Follow-up dates and follow-up counts are tracked per request, so your team knows at a glance which documents need a nudge and which are in hand.

AI-Powered Insurance Card Scanning

Here’s where it gets interesting. When an insurance card arrives — whether uploaded by the family or scanned by your staff — StreamABA’s AI vision model reads the card and extracts the fields automatically.

Screenshot: AI insurance card extraction review step

The extraction captures:

  • Payer name
  • Member ID
  • Group number
  • Policy number
  • Plan name
  • Subscriber name
  • Effective date
  • Copay
  • Phone number

The extracted payer name is fuzzy-matched against your practice’s payer directory, so “United Healthcare” and “UnitedHealthcare” and “UHC” all resolve to the same payer record.

Staff reviews the extracted data in a confirmation step before saving — no blind automation. But instead of squinting at a card photo and typing 8 fields by hand, they’re scanning a pre-filled form and clicking confirm.

If a card was uploaded weeks ago and the fields weren’t extracted at the time, the “Re-Extract” action runs the AI on the existing images. No need to ask the family for the card again.

One-Click Insurance Discovery

Sometimes the family doesn’t have their insurance card. Sometimes they have the card but the information is incomplete. Sometimes you need to verify whether coverage is active before spending time on a full VOB.

StreamABA integrates with Stedi’s Insurance Discovery API. One click submits the patient’s demographics — name, date of birth, sex, address — and returns any insurance coverage found.

For child patients (which is most of ABA), the system runs two parallel searches: one with the child as the subscriber, one with the child as a dependent under the guardian. Results come back with the payer name, member ID, group number, coverage status (active or inactive), plan dates, and coverage level.

Results are deduplicated and presented in a selection interface. Pick the right coverage, and the payer record is created on the lead automatically — pre-populated with the discovered data. From there, you move straight to benefits verification.

Benefits Verification Tracking

Every ABA intake requires a Verification of Benefits (VOB) before services can begin. StreamABA tracks the full VOB lifecycle on every payer attached to a lead:

  • Requested — staff initiates the VOB, timestamp recorded
  • Completed — verification data entered, including: coverage status, network status, preauthorization requirements, copay, coinsurance, deductible (amount and amount met), out-of-pocket maximum, annual maximums, session limits, and ABA-specific fields like maximum hours per year, sessions per week, and age limits

The VOB record captures the verification method, representative name, reference number, and free-text notes. When your staff calls a payer and spends 45 minutes on hold, the details of that call are recorded once and accessible to everyone on the intake team.

VOB completion is one of the four checkpoints in the intake completeness score. A lead can’t convert to a client without it.

Electronic Signatures and ROI

The Release of Information is often the first bottleneck in intake. You can’t request medical records from a PCP without a signed ROI. You can’t get a signed ROI without sending the form to the family. And every day that ROI sits unsigned is a day you can’t move forward.

StreamABA generates an ROI from your practice’s document template, pre-fills it with the family’s information — client name, date of birth, guardian name, contact details — and sends a signing link to the guardian via email or SMS.

The guardian opens the link, reviews the document, draws or types their signature, and submits. No printer. No scanner. No “I’ll bring it to the next appointment.” The signed document is immediately available on the lead’s record, and the system captures the signer’s name, IP address, user agent, and timestamp for compliance.

Signing links expire after 30 days and track their status — sent, viewed, signed, expired. If a guardian opens the link but doesn’t sign, your team can see that and follow up with a targeted nudge instead of a generic “did you get the form?” call.

The same e-signature system handles consent forms, restrictive procedure consent, and any other document your practice needs signed during intake. Each template supports custom form fields, merge tags, and multiple signature areas.

PCP Referral Faxing

Yes, faxing. PCPs still operate on fax. Calling that reality “outdated” doesn’t change it.

StreamABA’s PCP referral workflow handles the entire loop:

  1. Initiate the request from the lead profile — select the client, confirm the PCP (auto-populated from the lead’s provider records), and choose the send method
  2. Generate the PDF from your practice’s referral letter template, pre-filled with client name, provider name, provider address, and practice details
  3. Fax it directly — the system faxes the PDF to the PCP’s fax number without your staff touching a fax machine, printing a cover sheet, or walking to a shared office device
  4. Track delivery — fax delivery status (sent, delivered, failed) is tracked per request with failure reasons logged

If the PCP doesn’t have a fax number on file, the system falls back to email or generates a printable PDF for mailing. The follow-up date defaults to 7 days and creates a document request record that feeds back into the intake completeness score.

For multi-client leads (siblings), the system generates one referral per child, each addressed to that child’s PCP. One click, two referrals, two faxes.

Medical records requests work the same way — with one important gate: the system checks for a signed ROI before allowing the request. If no ROI is on file, the form explains why and blocks submission. If one exists, staff selects which signed ROI to attach to the outbound request. The ROI travels with the records request automatically.

Document Requirements by Payer

Not every payer requires the same documents. Some require a referral from a PCP. Some require a diagnosis report. Some require both, plus a signed consent for restrictive procedures.

StreamABA lets you configure document requirements per payer — or set organization-wide defaults. Requirements can include dependency rules (e.g., the ROI must be signed before medical records can be requested). When a lead has a specific payer attached, the conversion checklist reflects that payer’s specific requirements.

This means your intake coordinators don’t need to memorize which payers require what. The system tells them. And it blocks conversion until everything is in hand.

The Conversion Checklist

All of this comes together in a single gate: the conversion checklist. Before a lead can become a client, five conditions must be met:

  1. At least one client (child) record added
  2. Client information complete (name and date of birth)
  3. Primary insurance/payer on file
  4. VOB completed on the primary payer
  5. All payer-specific required documents collected

Screenshot: Conversion checklist with green checks and red X items

The checklist is visual — green checkmarks for met requirements, red X marks for gaps, with specific messages explaining what’s missing. It’s enforced at the system level, not just the UI. You cannot convert a lead to a client if the checklist isn’t complete.

This eliminates the failure mode where a client starts services but their insurance hasn’t been verified, or their ROI was never signed, or their referral is still pending. Every client that enters your clinical system has a complete intake record — because the system won’t let them in without one.

What Changes When Intake Is Automated

The individual features matter, but the compound effect is what changes intake timelines:

Day 1: Family submits interest. Lead created (automatically from web form, CRM sync, or manual entry). Workflow rule creates a task for the intake coordinator.

Day 1: Intake coordinator sends insurance card request via SMS (one click). Sends ROI for e-signature via email (one click). Runs insurance discovery if card not yet received.

Day 2: Family uploads insurance card. AI extracts payer data. Coordinator confirms. Insurance discovery returns active coverage. VOB process starts.

Day 2: ROI signed electronically. System auto-generates PCP referral and faxes it.

Day 3-5: VOB completed. Referral received. All document requirements met.

Day 5: Conversion checklist green across the board. One-click conversion to client. Ready to schedule.

Five days instead of thirty. Not because anyone worked harder, but because the waiting — the dead time between each step — was compressed by sending requests immediately, receiving responses electronically, and tracking everything in one system.


Want to see how fast your intake could move? Reach out at [email protected] — we’ll walk through your current workflow and show you where the time goes.

Follow us on LinkedIn and X for more product updates.

Live demo · No sales call

Ready to Streamline your practice?

Get instant access to a live demo of the all-in-one ABA platform built by clinicians, for clinicians. No sales call.

HIPAA compliant · Signed BAA · Built for ABA