Ask any admissions coordinator or intake specialist at an addiction treatment facility what eats the most frustrating hours of their day, and you will hear the same answer again and again:
Manual verification of benefits (VOB), and the phone tag that follows.
In the traditional intake model, a prospective patient messages or calls the facility. The coordinator collects the member ID, the subscriber details and the date of birth, writes them down or pastes them into a spreadsheet, then sends them to a billing team or keys them into payer portals one at a time.
Hours later, or the next morning if the inquiry came in after 5 PM, the answer comes back. Too often the policy is inactive, the deductible is out of reach, or it is a state Medicaid plan the facility does not take.
By the time the coordinator calls back, they get voicemail. The bed sits empty, staff time is gone, and the person who needed help has moved on.
The Mechanics of X12 270/271 Electronic Eligibility
HIPAA names the X12 270 and 271 transactions as the standard electronic eligibility question and answer, and health plans must accept the standard transaction:
- X12 270 (Health Care Eligibility Benefit Inquiry): The request sent from the provider or platform, carrying the patient’s name, date of birth and member ID, and the facility’s National Provider Identifier (NPI).
- X12 271 (Health Care Eligibility Benefit Response): The payer’s reply, returned through a clearinghouse such as Stedi: whether coverage is active, and the benefits listed by service type and network.
Hospitals and clinics have used 270/271 for years. Treatment admissions has a harder question to answer: not just whether the policy is active, but what it pays for the level of care you offer.
Inpatient or Outpatient: Reading the Benefits That Matter
An active policy is only the first answer. Admissions also needs to know what the plan pays for the care you provide.
When Automate Admits runs a check through Stedi, it also builds two short summaries from the benefits the payer returns, matching on the payer’s service type codes and benefit names:
1. Inpatient: detox and residential
Cost share the payer lists under inpatient service types, such as inpatient, residential, detox or psychiatric inpatient care: the in network deductible, coinsurance, copay and out of pocket maximum the payer returned.
2. Outpatient: PHP, IOP and OP
Cost share listed under outpatient service types, such as outpatient care, partial hospitalization, intensive outpatient, office visits or psychotherapy, with the same fields.
Notes the payer attaches, such as prior authorization, are listed with the result. The summaries are a starting point, not the final word: payers do not always break benefits out by level of care, some benefits fit neither group, and a broad service type can carry figures for other kinds of care. A 271 is also not a guarantee of payment or a prior authorization, so your team still confirms the details before admission.
Payer Checks: Why the Result Belongs in the Conversation
The biggest change comes when the check runs from the conversation and its result lands there, instead of waiting in a coordinator’s queue.
Consider the difference for the coordinator:
Traditional workflow: Coordinator answers call → gathers insurance → calls payer or logs into portal → waits hours → finds out the lead has an out of network HMO → calls the lead back → lead does not answer.
Automate Admits workflow: Lead messages the facility on Facebook or web chat → the AI agent answers, asks about their coverage and gets their phone number → the member ID and date of birth go on the contact: your coordinator adds them, or, only if your team turns this on, the AI asks for them once, after it has the phone number and only for a commercial plan → with automatic checks turned on, a real time Stedi 270/271 check runs in the background once the lead is hot or further along → the coordinator sees the result in the conversation (sample data: active commercial PPO, $1,250 deductible remaining) and can reach out right away.
State Medicaid Rules
Most treatment programs have firm rules about state Medicaid. A program may take its own state’s Medicaid plans and not a neighboring state’s.
You tell the AI agent which state Medicaid plans you take and which you do not. When someone mentions Medicaid, it answers for their state from that list instead of guessing, before any call is booked, so coordinators do not spend an intake call on a plan you cannot take.
HIPAA and 42 CFR Part 2 Handling
Handling substance use disorder inquiries electronically carries duties under the HIPAA Privacy and Security Rules and 42 CFR Part 2.
Automate Admits acts as a Business Associate under HIPAA and offers a standing Business Associate Agreement (BAA) to every customer. For Part 2 programs, Automate Admits acts as a Qualified Service Organization (QSO), and every account owner accepts our QSO agreement at signup. Part 2 consent management (consent records, revocation, segmentation) is not built into the platform, so those controls stay in your own systems and procedures.
PHI is encrypted in transit and at rest and stored on AWS. We hold BAAs with AWS, Paubox and Stedi. Not every channel has one: Facebook and Instagram messages pass through Meta, and texts and calls through Telnyx, and neither is covered by a BAA with us. We describe the platform as HIPAA eligible rather than HIPAA certified, because no government body certifies software. Our trust page lists every subprocessor and which ones have a BAA.
Conclusion: Transforming Admissions Efficiency
Automating verification of benefits does not replace the human empathy of your admissions team. It frees them from clerical data entry and endless portal logins so they can focus on what matters: counseling families, explaining treatment options, and guiding patients through the admissions door.