Call type insight
Non-Urgent Symptom Questions
Non-urgent symptom questions come from patients who feel unwell but not in danger: a rash that will not clear, a cough that lingers, a sore knee, a question about something new since their last visit. The caller wants to know whether to come in, wait, or try something at home. Answering that is clinical judgment, which a front desk should not supply and an AI receptionist must not. What the phone can do is record the symptom well, apply the practice's own rules, and get the caller to the right next step.
What these callers hope to hear
- •Whether the symptom is worth an appointment at all
- •Whether they can be seen today or later in the week
- •Whether a nurse can call them back with advice
- •Whether an over-the-counter remedy is safe to try
- •Whether the symptom is related to a medication or recent procedure
Every one of these is a clinical question, so the phone's job is routing, not answering.
How the symptom should be written down
- •In the caller's own words, without medical relabeling
- •When it started and how it has changed since
- •What makes it better or worse, as the caller describes it
- •Recent visits, procedures or new medications the caller mentions
- •The patient's age, when a parent or caregiver is calling
A nurse reading a clear record can decide faster than one returning a vague message.
Symptom rules the clinical team writes
- •Symptoms that always transfer to a nurse or the on-call line
- •Symptoms that always prompt the instruction to call emergency services
- •Reasons that can be booked as a routine visit without review
- •Questions that become a message to the care team for a callback
- •How after-hours symptom calls differ from daytime ones
These rules are the practice's clinical judgment, written once so the AI can apply them on every call.
How AI reception handles a symptom call
- •Listens and records the symptom without offering an opinion on it
- •Applies the practice's escalation list and transfers when a rule matches
- •Books a visit into the EHR where integrated, when the rules allow it
- •Takes a structured message for the nurse queue when a callback is the right step
- •Tells anyone who describes an emergency to hang up and call emergency services
Patients get a clear next step, and the clinical decision stays with clinicians.
Where symptom calls go wrong without structure
- •Front desk staff feel pressure to offer reassurance they are not trained to give
- •Messages say only that the patient called about a cough
- •Nurses spend their callback gathering basics the first call should have captured
- •Callers who cannot get through head to urgent care or the emergency department
- •A worsening symptom sits in a voicemail box overnight
The risk lives in the gaps between calls, and clear rules plus a complete record narrow them.
What to review with clinicians
- •Escalated symptom calls, and whether clinicians agreed with the route
- •Symptom calls from patients who called back later feeling worse
- •How long nurse callbacks take for symptom messages
- •Reasons that keep producing messages and could become booking rules
Reviewing escalations with clinicians is how the rule list improves over time.
Routing checklist
Keep this call type consistent across shifts with a short routing checklist.
- •Define required intake fields for this call type.
- •Set escalation rules and approved handoffs.
- •Confirm where summaries and tasks are logged.
- •Measure resolution time and update scripts regularly.
Frequently asked questions
Will the AI tell a patient whether their symptom is serious?
No. It does not assess symptoms or give medical advice. It records what the caller describes, applies the escalation rules the practice wrote, and routes the call to a nurse, the on-call line, a booked visit or a callback message. If the caller describes an emergency, it tells them to hang up and call emergency services.
Who writes the escalation rules?
The practice's clinicians. During setup, MedReception works from the practice's own protocols for which symptoms transfer, which book and which become messages. The rules can be adjusted as the clinical team reviews how calls were actually handled.
What happens with symptom calls after hours?
The AI answers day and night. After hours it follows the practice's after-hours rules, which might send certain symptoms to the on-call clinician and turn the rest into messages for the morning team, with the emergency instruction for anything the rules treat as an emergency.
Bottom line
Symptom questions deserve a careful listener and a clinical decision, in that order. Have the clinical team write which symptoms transfer, which book and which become messages, then let the AI apply that list on every call. Patients get a clear next step, and nurses get a complete record instead of a guess.
More call types to explore
View all call types →Map adjacent scenarios so your routing, staffing, and automation rules stay consistent.
Phone problem guides
Map each call type to the phone problem it causes.
Explore the Phone Problems hub to see how missed calls, long holds, voicemail overflow, and staffing gaps show up in daily call patterns.
Solve the phone problem next
Turn this call type into a system-level fix
These phone-problem guides stay within two clicks so you can show leadership exactly how this scenario gets resolved end to end.
Phone problem fix
Missed calls spiral
Stop overflow before it hits voicemail with 24/7 coverage and structured intake.
Open →Front desk relief
Front desk overload playbook
Route routine calls to AI so staff can focus on in-person patients.
Open →After-hours plan
Voicemail overflow cleanup
Capture every caller after hours and deliver summaries before staff log in.
Open →