AI Receptionist in Chapel Hill, NC: Referral Intake

A referral call is not a patient call, and your phone cannot tell the difference

Most phone setups treat every inbound call as a patient. In a town built around a public research university, a practice line carries something else too: coordinators, schedulers, and nurses calling from other offices to hand a patient over. That call has a different shape. It is one professional passing another a case, and what it needs captured is not a date of birth and a symptom but a referring provider, a working reason, what records have already moved, and how soon this needs to be seen. Dropped into the same queue as a refill request, it waits behind calls that could have waited themselves, while the person on the other end stands in front of a patient promising someone will call. MedReception AI answers in under a second and takes unlimited simultaneous calls, so a referring office never meets a busy signal or a hold loop. From the first question the call can branch down a path built for referrals instead of the general patient script.

What a referral intake actually has to ask

A referral captured badly costs two more phone calls. Build the branch to collect what your coordinator needs before she can do anything: the referring practice and provider, a direct callback line that reaches a human rather than that office's main menu, the reason for the referral in the referring clinician's own words, whether records or imaging have already been sent and by what route, the patient's coverage and whether an authorization is in flight, and the timeframe the sender has in mind. We build on more than thirty specialty templates, so a sports medicine office and a gastroenterology office ask different questions and both sound like themselves. What the AI never does is decide whether a referral is urgent, offer a clinical opinion, or write anything into a chart. It gathers and structures. Your coordinator opens a complete record and books the visit, instead of starting a round of phone tag just to learn the basics.

Your call volume follows the academic calendar, not the average week

Chapel Hill is home to the University of North Carolina at Chapel Hill, a public research university whose campus includes schools of dentistry, nursing, pharmacy, and public health. A practice here inherits that rhythm whether or not it treats students. Late summer brings a wave of people establishing care in a new town all at once: new patient calls, requests to pull records from a physician three states away, forms and documentation, and coverage questions from patients on a plan they just enrolled in. Spring's end brings the mirror image, people leaving, asking about prescription continuity and where their chart goes next. Then the summer trough. A fixed front desk cannot flex across that curve. Staff for the peak and you pay for idle phones in July; staff for the average and August buries you. Coverage that runs 24/7 with unlimited concurrent calls absorbs the surge without a seasonal hire, and dozens of languages are handled natively for the international students, visiting scholars, and families a university town draws.

Closing the loop with the office that sent you the patient

The second half of coordination is the part that eats a coordinator's day: did you get our referral, has the patient been scheduled, when is the appointment, can you send the consult note back. Every one is legitimate, and every one interrupts the person actually doing the coordinating. Katie can field the defined status questions you authorize her to answer, releases nothing you have not authorized, and captures the rest with the identifying details attached so the callback goes out with an answer already in hand. Victoria turns voicemail into the same readable summary, Sallie handles the scheduling back-and-forth, and Annie covers the line after close so a Friday evening referral is logged rather than lost. Every call ends as a structured summary your MA can paste into the chart. The system stays EMR-independent by design: live and currently deployed on some systems, available through API or FHIR on others, and available through secure workflow automation where no direct interface exists. A HIPAA BAA is included, with AES-256 at rest and TLS in transit.

Bring the referral calls to the demo, not the easy ones

Anyone can demo a question about office hours. Book a MedReception AI demo and bring the calls that actually cost you: a coordinator from another practice trying to hand off a semi-urgent consult at four forty-five on a Friday, the August week when every new arrival in town calls at once, the third status check on a patient who was scheduled two weeks ago. You will hear exactly where the referral branch splits off from the general patient script, which fields come back on the summary, how an urgent caller escalates to a human on the rules you set, and where clinical judgment stays firmly with your staff. If it fits, our team builds it around your referral workflow and your intake questions, and edits stay free for the lifetime of your account, so the script keeps up as your referral relationships change. Schedule the demo and put a line that answers in under a second in front of the offices that send you patients.

Referral Intake and 24/7 Coverage for Chapel Hill Practices

A referral call is not a patient call, and your phone cannot tell the difference

What a referral intake actually has to ask

Your call volume follows the academic calendar, not the average week

Closing the loop with the office that sent you the patient

Bring the referral calls to the demo, not the easy ones

Related reading

Bring this to your practice