Flu, strep, COVID, and RSV calls are same-day visit decisions

Start with the same-day choice moment

A patient asking about flu, strep, COVID, RSV, sore throat, cough, fever, rapid testing, online check-in, insurance, a school note, a work note, or a result callback is often deciding where to go today. The call may sound administrative, but the intent can be local, urgent, and perishable.

The goal is not to let AI make clinical decisions. The goal is to answer quickly, collect the right context, and get the caller into the clinic's approved next step before they call another urgent care.

• Which test or symptom is the caller asking about?
• Does the caller want same-day care, online check-in, a result callback, documentation, or staff review?
• Which location, payer, form, school timing, work timing, and callback number apply?
• Did the caller ask a question that staff must answer?

Sort the call before the desk has to restart it

A strong respiratory testing call path does not treat every caller as the same callback. It separates visit-ready testing questions, online check-in blockers, payer questions, result callbacks, school or work documentation, and staff-only clinical questions in the first minute.

That matters because the front desk needs useful context, not another blank missed number. The caller should hear the clinic's approved next step, and staff should see the reason the call needs a visit, a callback, a document review, or a clinical handoff.

• Same-day visit and online check-in requests
• Flu, strep, COVID, RSV, multiplex, or unsure test requests
• Result, school-note, work-note, portal, and documentation callbacks
• Insurance, self-pay, accepted-plan basics, and exact-cost exceptions
• Test choice, result interpretation, medication, clearance, and care-level questions for staff

Build the model around testing-call volume

The simple model starts with monthly testing calls, visit-ready or staff-callback share, a conservative immediate-answer lift, and average net revenue per visit. HIDA's urgent-care overview lists $132 in average net revenue per visit as a public planning input before clinics replace it with their own data.

Example: 520 monthly flu, strep, COVID, RSV, symptom, result, school-note, work-note, and after-hours calls x 41% visit-ready or callback intent x 25% lift x $132 average net revenue per visit equals about $7,036 in monthly recovered same-day visit value. That is a planning model, not a promise.

• Testing-call volume by clinic, daypart, season, and channel
• Visit-ready share after filtering records, billing, results-only, and unsupported clinical questions
• Average net revenue per visit by payer, visit type, lab, imaging, and occupational medicine mix
• Online check-in use, callback speed, staffing coverage, and approved result-handling rules

Flu and COVID questions need clear limits

CDC flu diagnosis guidance says flu symptoms can overlap with other respiratory illnesses and that multiple tests can detect influenza viruses. CDC COVID testing guidance separates NAAT and antigen tests and notes that a single negative antigen test may need repeat testing under FDA recommendations.

Those facts are useful for policy design, not for improvising on a live call. The AI should answer only approved access questions, capture what the caller wants, and send test choice, interpretation, treatment, and clearance questions to staff.

Respiratory virus testing has different test types

CDC respiratory virus testing guidance explains that antigen tests often return results quickly, NAAT or PCR tests detect genetic material, and multiplex tests can detect more than one virus. It also notes that antigen tests are often less sensitive than NAATs.

That complexity is exactly why the first phone path should be conservative. The AI can capture the requested test, exposure context, symptoms in the caller's words, timing need, and payer context without promising test availability, accuracy, result timing, or what a result means.

Strep testing calls are not diagnosis calls

CDC testing guidance for strep throat and scarlet fever says healthcare providers may use a rapid strep test and sometimes a throat culture. That means a caller asking for a strep test still needs the clinic's staff-directed path, not an AI diagnosis.

For urgent care, the safe call plan is to collect sore throat, fever, rash, exposure, school timing, work timing, and test request context, then let staff decide the clinical and testing next step.

• Sore throat, rash, fever, stomachache, or exposure language
• Preferred clinic, online check-in status, payer, and callback number
• Result, antibiotic, throat culture, school-return, work-return, and family questions for staff

RSV and respiratory panel calls need extra handoff context

CDC RSV diagnostic testing guidance says RSV symptoms are nonspecific and can overlap with other viral and bacterial infections, and that NAATs and antigen tests are commonly used clinical laboratory tests.

The AI should not tell a caller which test is needed or whether a symptom pattern is safe. It should preserve concern language, timing, test request, location, payer, and callback need so staff can apply approved rules.

Result, school-note, and work-note calls need a separate path

Testing demand does not end when a patient leaves the clinic. People call back about result status, what a result means, whether documentation can be sent, whether school or work will accept a note, and whether another family member needs to be seen.

Those calls can be organized without giving unauthorized answers. Capture caller identity, visit context, result question, documentation need, school or work deadline, preferred callback window, and staff-only question.

Phones concentrate the front-desk bottleneck

MGMA's March 2026 practice-leader poll found eligibility, prior authorization, and scheduling were the most time-consuming medical-practice phone tasks. MGMA's patient-access guidance also discusses phone access, routing, callbacks, dashboards, and AI-enabled support.

Testing calls often combine all of those pressures: scheduling, payer details, forms, result callbacks, work notes, school notes, and clinical exceptions. A clean call path reduces repeat interruptions while protecting the staff handoff.

The market gives patients alternatives

UCA reported 15,032 open urgent-care centers in January 2025. HIDA reports more than 200 million annual urgent-care visits, and Experity's 2026 visit dashboard describes demand as both seasonal and structurally elevated.

In many communities, a patient can compare urgent care, primary care, retail clinic, telehealth, and emergency options while waiting for a callback. A fast, bounded first answer can preserve the visit without making medical promises.

What staff should see before they respond

A useful testing-call summary should include caller name, callback number, preferred clinic, main concern, requested test, symptom words, onset or exposure timing, online check-in status, payer or self-pay context, school or work deadline, and any result or documentation request.

That context lets staff choose the next operational step: invite online check-in, clarify visit rules, prepare forms, send a result callback, hand payer questions to billing, ask a clinician to review, or use the clinic's approved emergency-care language.

• Requested test: flu, strep, COVID, RSV, multiplex, or unsure
• Caller concern, timing, location, payer, form, deadline, and callback window
• Staff-only items: test choice, result interpretation, medication, clearance, benefits, exact cost, records, and care level

Measure the first 30 days by recovered next steps

The first month should not be measured by raw call volume alone. Measure answered testing calls, abandoned-call reduction, same-day visits, online check-ins, result callbacks, staff escalations, payer-detail capture, note requests, and callback speed.

The practical win is when callers get a credible next step fast and staff receive a structured summary instead of a bare missed number.