Key takeaways
- Separate quick chat from tasks: anything a patient is waiting on needs an owner, a due time and a closed status.
- Route messages to roles and pools, not individuals, so work survives sick days and turnover.
- Every phone message should carry the same fields: patient, callback number, reason, urgency and who took it.
- Pick a tool with individual logins, audit logs and a BAA, then measure open tasks older than one business day.
What sticky notes cost you
Most practices still run on a mix of sticky notes, hallway handoffs, personal text messages and an EHR task list that only half the team uses. Each works until it does not. A note falls behind the monitor. A text to a nurse's personal phone holds a patient's name and medication. A refill request taken at 4:55 on Friday is still waiting on Tuesday because nobody knew it existed.
- No owner: a message addressed to the nurses belongs to nobody in particular.
- No time stamp: nobody can tell how long the patient has been waiting.
- No status: there is no way to see what is done and what is still open.
- No privacy: patient details sit on desks or in personal phones.
- No record: when a patient says they called three times, there is nothing to check.
The volume is growing
Internal messages multiply as patient messages grow. In early 2025, 70% of medical groups reported an increase in patient portal message volume over the prior year, and only 1% reported a decrease[1]. Each portal message, phone call and fax that needs a clinician's answer becomes an internal handoff.
- Reported an increase in portal message volume 70%
Source: Medical Group Management Association (MGMA), 2024[1]
Show the data
| Item | Value |
|---|---|
| Reported an increase in portal message volume | 70% |
Clinicians already spend a large share of their day on this. In one study of primary care physicians, inbox management took 85 minutes a day, 23.7% of their EHR time[2]. A poorly structured staff message, missing a callback number or a reason, adds a second round trip to work that is already crowding the day.
Messages and tasks are different things
The single most useful rule is to separate conversation from work. Quick questions between colleagues can live in chat. Anything a patient or another office is waiting on is a task, and a task needs an owner, a due time and a closed status.
| Type | Example | Where it lives | Owner | Close within |
|---|---|---|---|---|
| Quick question | Is Dr. Patel running late? | Secure chat | Whoever answers | Minutes |
| Patient callback | Patient asks about a lab result | EHR task on the chart | Clinical pool | Same business day |
| Refill request | Pharmacy fax or patient call | EHR task on the chart | Refill pool | Per refill policy |
| Scheduling request | Move Thursday's visit | EHR task or schedule queue | Front desk pool | Same business day |
| Billing question | What is this charge? | Billing queue | Billing lead | Two business days |
| Urgent clinical concern | New chest pain reported | Not a message: warm transfer | Nurse or provider now | Immediately |
Write your own version of this table and pin it at every workstation. Staff should never have to decide on the spot where a message goes.
Route to roles, not people
A message sent to one person stalls when that person is out. Turnover makes this worse: 29% of medical group leaders reported higher staff turnover in 2026 than in 2025[3], and medical assistants and front-desk roles remain the most common churn points[3]. A message addressed to a role or pool, such as clinical callbacks or refills, survives sick days, vacations and resignations.
- Create pools that match your table: clinical callbacks, refills, scheduling, billing, referrals.
- Give each pool a daily owner and a backup on the schedule.
- Allow direct messages to individuals only for questions, not for patient work.
- When someone leaves, their open tasks move to the pool on their last day, not weeks later.
The fields every phone message needs
Most callbacks fail because the message is incomplete. Build a template with required fields so staff cannot send a message without them.
- Patient name and date of birth, linked to the chart.
- Caller name and relationship, if not the patient.
- Callback number, confirmed by reading it back, and the best time to call.
- Reason category from a short list, plus the caller's own words.
- Urgency: routine, same day, or transferred now.
- Pharmacy, if the request involves a prescription.
- Who took the message, and when.
Example: 'Callback, same day. Patient: Jordan Lee, DOB on chart. Caller: patient. Number: confirmed mobile on file, best after 3 pm. Reason: results question. Patient says: wants to know if the blood test from Monday needs a follow-up visit. Taken by: front desk, 10:42.' Everything the nurse needs is there, so one call closes it.
What should never be a message
Some calls cannot wait in any queue. Agree a short list with your clinical lead and train it until it is automatic. A caller describing a possible emergency is told to hang up and call 911. A caller with an urgent but not emergency concern, such as a high fever in an infant, is transferred live to a nurse or provider, and the transfer is logged afterwards. A message is the record of the call, never the way urgent clinical information travels.
Choosing the tool
Many practices already own the right tool: the EHR's task or message center. Use it for patient work, because it keeps the message on the chart. A separate secure chat app can work well for quick coordination between rooms and sites. Personal text messages should be off limits for anything involving a patient.
- Individual logins with multifactor authentication; no shared accounts.
- Messages tied to the patient record where patient work is involved.
- Pools, due times, status and escalation when a task sits too long.
- An audit log showing who created, viewed, reassigned and closed each item.
- Remote wipe and screen lock for mobile apps.
- A business associate agreement from any outside vendor.
Any outside messaging vendor that stores patient information for you is a business associate. A covered entity may let a vendor handle that information only with satisfactory assurance, in a business associate agreement, that the vendor will safeguard it[4].
Audit trails and retention
The audit trail is what turns a messaging tool into a record. When a patient says they called three times, you can check. When a task sat for four days, you can see where. Set retention deliberately: messages filed to the chart follow your medical record retention rules, while chat that never touched patient work can be deleted on a shorter schedule. Write the policy down; HIPAA requires covered entities to keep required policy and compliance documentation for six years[5].
A 30-day rollout
Days 1 to 5: agree the rules
Build your message-type table, pools and required fields with one clinician, one front desk lead and one biller.
Days 6 to 10: configure
Set up pools, templates and escalation timers in the EHR or chosen tool. Remove access for former staff.
Days 11 to 15: train
Two short sessions per role, using real-looking fictional messages. Practice the urgent-call rule out loud.
Days 16 to 25: go live
Ban sticky notes for patient work. A daily owner checks each pool at opening, lunch and close.
Days 26 to 30: review
Look at open tasks, time to close and incomplete messages, then adjust the template and pools.
Escalation when a task sits too long
Routing only works if someone notices when it fails. Set an escalation rule for each pool: when a task passes its close-within time, it turns red on the pool view and notifies the pool's backup. When it passes twice that time, it notifies the practice manager. Keep the rule simple enough that staff can explain it.
- Morning huddle: the daily owner reads out the count of overdue tasks in each pool, nothing more.
- Midday sweep: the backup clears or reassigns anything that turned red before lunch.
- End-of-day handoff: open same-day callbacks are either completed or the patient is told when to expect the call.
- Friday check: the manager reviews anything older than three business days and asks why, without blame.
Escalation is also how you discover that a pool is understaffed. If refills turn red every afternoon, the fix is a schedule change, not a reminder to work faster.
What to measure
- Open patient tasks older than one business day, checked every morning.
- Median time to close, by pool.
- Share of messages sent back for missing information.
- Repeat calls from the same patient about the same issue within a week.
- Messages sent outside approved tools, reported without blame so you can fix the cause.
Example: a fictional four-provider family practice began with 37 open callback tasks older than one business day. After three weeks of pooled routing and required fields, the morning count averaged under ten, and repeat calls about results fell noticeably. The biggest single fix was the confirmed callback number field.
Frequently asked questions
Is texting colleagues about patients allowed?
Only through a secure tool your practice controls, with individual logins, audit logs and a business associate agreement from the vendor. Personal text messages should never carry patient information.
Should we use the EHR task list or a separate chat app?
Use the EHR for anything a patient is waiting on, because it keeps the message on the chart. A secure chat app is useful for quick coordination between staff that does not involve patient work.
How do we stop messages getting lost when staff leave?
Route patient work to pools and roles instead of individuals, and move any remaining tasks to the pool on the person's last day.
What is the most common problem with phone messages?
Missing details, especially an unconfirmed callback number and a vague reason. Required template fields fix most of it.
References
Medical Group Management Association (MGMA) (2024). Ensuring accurate coding and billing for patient portal messages as e-visits (opens in a new tab) ↑
Annals of Family Medicine (2017). Tethered to the EHR: Primary Care Physician Workload Assessment Using EHR Event Log Data and Time-Motion Observations (opens in a new tab) ↑
Medical Group Management Association (MGMA) (2026). Stabilized but not solved: Staff turnover in medical practices looking no better, no worse (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.502 - Uses and disclosures of protected health information: General rules (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.530 - Administrative requirements (opens in a new tab) ↑