The OB Intake Call and What It Has to Get Right

OB intake is the highest-stakes routine call an obstetrics practice takes, and it usually gets handled by whoever picked up the phone.

A patient calls to say she is pregnant. In the next few minutes someone has to register her if she is new, work out which provider class she belongs with, pick the right first appointment type, and offer a date that fits a window nobody has told her about. Getting any one of those wrong sends her into a visit that has to be rebooked, or into a schedule slot that was never meant to hold her.

One call, four decisions, and none of them are obvious

The reason this call is hard is that it compresses several unrelated determinations into one conversation with a patient who is often calling for the first time.

She may be an existing patient of the practice or entirely new, which changes whether registration has to happen before anything else. She may be asking for a specific physician by name because a friend recommended them. She may have a date in mind based on something she read. And the practice has its own rules about what the first prenatal visit is, how long it takes, and who conducts it.

None of that is visible to her, and most of it is not written down anywhere the person answering can see. It lives in the practice’s operating knowledge, which is to say in the heads of the schedulers who have done this longest.

The consequence is variance. The same call handled by two different people produces two different appointments, and the practice only learns which one was wrong when the patient arrives for a visit that does not match what she needs.

Registration has to happen first, and it is genuinely front-office work

Before an appointment can be offered to a new prenatal patient, she has to exist in the system.

That is a registration task, done through POST /patients, and it is exactly the kind of structured capture a call handles well. Name, date of birth, contact details, address, coverage, preferred language, and consent to be contacted are all things the patient can state and the system can record while she is on the phone.

Coverage capture at this moment carries more weight in obstetrics than elsewhere. Medicaid is the largest single payer of pregnancy-related services, financing 41% of births nationally in 2023 and nearly half of births in rural communities. For a large share of OB intake calls, the coverage question is the one that determines whether care starts on time.

Doing it during the call rather than after it matters more in obstetrics than in most specialties, because the follow-on work is heavy. Records need to be requested from a previous practice. Insurance needs verifying against a plan that may be new. Forms need sending. Each of those depends on the patient record existing, and each of them starts a clock.

There is a scheduling rule attached that is worth respecting rather than working around. New patients commonly cannot book inside a few business days, specifically so their paperwork can be completed first, while established patients can often book next business day. A first prenatal visit booked too soon is a visit where nothing can be done because nothing arrived.

The complication: gestational age decides who she can see

This is the rule that makes OB intake different from every other new-patient call, and automation that does not know it will book confidently and wrongly.

Many OB/GYN practices route new patients and symptom visits to nurse-midwives and nurse practitioners, so physicians can concentrate on procedures and higher-risk patients later in pregnancy. Elsewhere the same idea appears as a rule that visits past a certain point in pregnancy are physician-only. Either way, a threshold in the pregnancy flips which providers are bookable, and it flips partway through an episode of care that may last most of a year.

So the intake call has to establish roughly where in the pregnancy the patient is, because that single fact determines the eligible provider set and therefore the available slots. Asking for a last menstrual period date or an estimated due date is a factual question, and capturing the patient’s answer is data collection.

The line to hold is what happens next with that number. The automation uses it to filter which providers and appointment types are bookable under rules the practice configured. It does not tell the patient what her gestational age means, does not assess whether her pregnancy is high risk, and does not decide that she needs a physician on clinical grounds. Where the answer is ambiguous, where she is unsure of dates, or where she volunteers anything about symptoms, the call goes to clinical staff. That handoff is not a failure of the automation. It is the design.

Asking for a specific provider is a conversation problem

A large share of these calls open with a patient asking for a named physician, and the answer is frequently that the physician is not available to her.

The reason might be a closed panel, a ramp cap, a provider who does not take new obstetric patients, or simply nothing open inside the window she needs. Whatever the cause, not accepting new patients is a conversation-design problem rather than a flag to be read aloud. A caller told flatly that a doctor is unavailable hears a brush-off and calls a different practice.

What works is language that redirects to the providers who do have availability without dismissing the request, and that explains the practice’s model rather than the constraint. In an OB practice with a midwifery team, that explanation is usually welcome once someone gives it.

The underlying data problem is worth naming too. The provider roster on a practice website and the provider roster in the system frequently disagree, and reconciling who actually works there and takes appointments is step one before any routing rule can be written. Automation applied on top of a stale roster produces confident answers about people who left.

Where OB call volume actually sits

Obstetrics generates more inbound contact per patient than most specialties, and the intake call is only the first of many.

In a March 10, 2026, MGMA Stat poll of practice leaders, the most time-intensive phone tasks were eligibility and prior authorization at 45%, scheduling at 31%, intake at 9%, prescription refills at 6%, and an other category at 9%. The poll had 294 applicable responses.

Intake looks small on that list until you account for how much scheduling and eligibility work a single OB intake sets in motion. One completed intake creates a registration, a coverage check, a records request, a first appointment, and the beginning of a visit series that will run for months. Measured by downstream work created, it is the most consequential call the practice takes.

That is the argument for handling it well rather than quickly. An intake call that captures the right information the first time removes several follow-up calls. One that does not creates them, and those calls land on the same staff a week later when the correction is more expensive.

What good looks like on a report

The natural metric is intake calls handled, and it will tell you almost nothing. Volume is set by how many people are pregnant, not by how well you work.

The number that reflects quality is the share of first prenatal visits that happen as booked, without being rebooked or converted to a different appointment type after the fact. Rebooking is the visible symptom of an intake call that captured the wrong thing, and it is countable.

Two supporting measures help. Time from intake call to completed registration, which should be zero because it should happen on the call, tells you whether the practice is deferring work it could finish live. And the share of intake calls transferred to clinical staff is worth watching in both directions: too high suggests the routing rules are underconfigured, and near zero suggests the automation is answering questions it should be handing off.

Key Takeaways

Treat OB intake as four decisions compressed into one call: registration, provider class, appointment type, and timing. Handling them implicitly is what produces variance between schedulers.
Register the patient during the call rather than after it. Records requests, coverage checks, and forms all depend on the record existing, and each starts a clock.
Respect the new-patient lead-time rule. A first prenatal visit booked inside the paperwork window is a visit where nothing can be done.
Capture an estimated due date or last menstrual period as a factual field, because it determines which providers and appointment types are bookable under the practice’s own rules.
Never let the automation interpret that date. It filters bookable slots; it does not assess risk, explain what gestational age means, or decide anyone needs a physician.
Hand off on ambiguity: unsure dates, anything about symptoms, or a request that does not fit a configured rule goes to clinical staff.
Script the redirect when a named provider is unavailable. A flat no sends the patient to another practice, and this is a conversation-design problem rather than a flag.
Reconcile the provider roster before writing routing rules. The website and the system disagree at most practices, and automation on a stale roster books people who left.

The OB intake call is worth more attention than it gets because everything downstream inherits its accuracy. A registration completed on the call removes three follow-ups. A first appointment matched to the right provider class and the right visit type prevents a rebooking the patient experiences as disorganization at a moment she is paying close attention. An AI team working inside athenaOne can register the new patient while she is on the line and capture the dates that determine which providers are bookable. It applies the practice’s own provider-class and lead-time rules instead of a scheduler’s memory of them. It redirects gracefully when a requested physician is unavailable, and hands anything clinical to the staff who should be hearing it.

Sources