A referral comes in on Monday, the first session is booked for Thursday, and the insurance check happens when the first claim bounces. The fix is one gate, not a reminder.
A behavioral health practice loses money in week six for a decision skipped in week one: a patient was scheduled before insurance eligibility was verified. The intake process lives in Zoho CRM as a Blueprint, and one transition, verify eligibility, with three mandatory fields is the whole control. The clinical record stays in the clinical record system.
Each chapter starts the video at that point.
Here is a pattern every behavioral health practice knows. A referral comes in on Monday. The intake coordinator calls the family, gets the history, and books the first session for Thursday because the calendar had a slot. The insurance check happens on Wednesday, or the following week, or when the first claim bounces. Six weeks later the claim is denied, the sessions have happened, and the practice is either writing off the money or having a very hard conversation with a family. The fix is not a reminder and it is not a spreadsheet.
It is one gate in the process that will not let a patient onto the calendar until someone has verified eligibility and written down what they found. Everything on screen is a mock demo of Zoho CRM with sample data. The clinical record never appears, because it lives in the clinical record system and stays there. This is the intake pipeline drawn as a Blueprint in Zoho CRM. A Blueprint is a process the system enforces. It has states, which are where a record can be, and transitions, which are the only ways to move between them.
The states here are the ones the practice already uses in conversation: referral received, contacted, eligibility verified, scheduled, first session complete. Nothing invented. The difference from a form is that a record cannot jump. It cannot go from contacted to scheduled, because there is no transition between them. The only road to scheduled runs through eligibility verified. That is the whole design decision, and it took the practice about an hour to agree on it. Everything else in this video is what that one decision does. There is one more thing a Blueprint gives you that a form never will.
Every record shows where it is. The coordinator, the scheduler and the practice manager all see the same word, eligibility verified or not yet, and none of them has to ask anyone. Open the transition. This is the editor for the step called verify eligibility, and it has a list of fields that must be filled before the transition can complete. Three of them. The payer, chosen from a list, not typed. The verification date. And the reference number from the call or the portal. Each one is mandatory, which in Zoho CRM means the transition will not finish without it.
Notice what is not on the list. There is no field for the clinical history, because that lives in the clinical record system. There is no field for the benefits detail, because the reference number is how you find that later. The gate asks for the three things that prove a person checked, and nothing that would make people skip it. Here is the same thing from the coordinator's side. She has finished the intake call and she clicks verify eligibility on the record. A small window opens asking for the three fields.
If she has done the check, she fills them in and the record moves to eligibility verified, and the scheduling step becomes available. If she has not done the check, she cannot make something up: the payer is a list, the date is a date, and the reference has to come from somewhere. And if she tries to schedule anyway, there is no button for it. Scheduled is not reachable from where the record is. That is the difference between a policy and a control. A policy says please verify first.
A control means the calendar does not exist until you have. One practical note. The coordinator is not slowed down by this. The three fields take under a minute to fill when the check has been done, and they replace the note she used to write anyway. What changes is only that the calendar waits for them. Once the transition completes, two things happen without anyone asking. The scheduler gets the record in her queue with the payer and the reference already on it, so the first question she used to ask, was this verified, no longer needs asking.
And the record carries the verification date, so when the first claim goes out, billing can see that eligibility was checked eleven days before the session, by whom, with what reference. That is what turns a week-six denial into a week-one conversation. If the payer says no on Wednesday, the family hears it on Wednesday, before anyone has been seen, and the practice has not delivered sessions it will not be paid for. One line on what this is not. The clinical record system holds the clinical record. Diagnoses, notes, treatment plans.
None of that moves into Zoho CRM, and the intake Blueprint never asks for it. What runs in Zoho is everything around the clinical record that decides whether the practice gets paid and whether the family is looked after: the referral, the contact, the check, the schedule, the follow-up. Two systems, one clear line between them, and a process on the operations side with gates. That is the same design as the behavioral healthcare solution on our site, and this transition is the smallest piece of it. If your practice has ever had a denial that started with a booking made too early, the fix is one transition with three fields, and it takes an afternoon to build on a system you may already own.
We build the intake process with the practice in a no-risk discovery: you pay only if you go ahead. The link is below, and so is the longer video on the whole path from intake to billing.
Because the patient was scheduled before eligibility was verified. A referral arrives on Monday, the coordinator books Thursday because the calendar had a slot, and the insurance check happens later or when the first claim bounces. Six weeks on, the claim is denied, the sessions have happened, and the practice either writes off the money or has a hard conversation with a family. The loss in week six comes from a decision skipped in week one.
The intake drawn as states and transitions the system enforces: referral received, contacted, eligibility verified, scheduled, first session complete. A record cannot jump from contacted to scheduled because there is no transition between them; the only road to scheduled runs through eligibility verified. That is the difference between a policy and a control. A policy says please verify first. A control means the calendar does not exist until you have.
The payer, chosen from a list rather than typed. The verification date. And the reference number from the call or the portal. Each is mandatory, so the transition will not complete without them, and none can be invented: the payer is a list, the date is a date, and the reference has to come from somewhere. Nothing clinical is asked for, and no benefits detail, because the reference number is how that is found later.
No. Diagnoses, notes and treatment plans stay in the clinical record system, and the intake process never asks for them. What runs in the operations system is everything around the clinical record that decides whether the practice gets paid and the family is looked after: the referral, the contact, the eligibility check, the schedule and the follow-up. Two systems, one clear line between them, and gates on the operations side.
No. The three fields take under a minute when the check has been done, and they replace the note she used to write anyway. What changes is that the calendar waits for them. Once the transition completes, the scheduler gets the record with the payer and reference already on it, and billing can later see that eligibility was checked, on what date, by whom. If the payer says no, the family hears it before anyone has been seen.
We design, build, integrate and operate AI-driven, platform-agnostic integrated business solutions for operationally complex companies. Start with a conversation; we will tell you if we are a fit.
