Someone calls your community and says, “Can I speak to a nurse?” The person answering that phone is almost never a nurse. They are a receptionist, a concierge, a business office manager covering the desk at lunch, or an evening associate who also has a resident at the counter asking about the dinner menu.
That person has about fifteen seconds to decide whether this is a 911 call, a get-the-nurse-right-now call, or a message with a callback window. They should not be deciding anything clinical. They should be running a pathway you built for them in advance.
Most communities do not have that pathway written down. What they have is a good receptionist who usually gets it right, and a hope that whoever is covering the desk on a Saturday night gets it right too. This is how you replace that hope with a script.
The three questions your front desk asks first, every time
Before anyone transfers a call, takes a message, or walks down the hall to find the nurse, they ask three things in this order. The order matters, because the third question is the one that changes everything.
- Who is calling? Name and relationship to the resident. Plus the best callback number, confirmed by reading it back.
- Which resident is this about, and where are they right now? Their apartment, the dining room, out with family, at a doctor’s appointment. The nurse’s first move depends on whether the resident is in the building.
- Is anyone in immediate danger right now? Asked plainly, with the specific words listed in the next section. This is the question that separates an escalation from a message.
Open with something that tells the caller the questions are not a stall. The wording your staff use in the first ten seconds sets the tone for the whole call:
“Absolutely. I’m going to get this to our nurse. So they have what they need before they call you, let me take three quick things. Can I start with your name and your relationship to the resident?”
Notice what that does not say. It does not say “the nurse is busy.” It does not say “I can only take a message.” It does not promise a transfer that may not be possible. It commits to a next step and explains why the questions exist.
Ban these five phrases at the desk outright. They are the ones that turn a routine call into a complaint to your regional director:
- “We’re short-staffed right now.”
- “The nurse is busy.”
- “You’ll have to call back tomorrow.”
- “That’s not something I can help with.”
- “I can only take a message.”
The escalate-now list: words that stop the intake
Some calls should never reach question three in a calm voice, because the caller already answered it in their first sentence. Every person who answers your phone should know this list cold, printed and taped where they can see it.
Stop the intake and escalate immediately if the caller mentions any of these:
- Chest pain, chest pressure, or chest tightness
- Trouble breathing or shortness of breath
- Not waking up, unresponsive, or passed out
- Face drooping, one-sided weakness, or sudden trouble speaking
- Bleeding that will not stop
- A fall with a possible head injury, or a resident on the floor who cannot get up
- Choking, or a severe allergic reaction
- Any statement about wanting to die or harm themselves
Two different things happen depending on where the resident is, and staff need both branches.
If the resident is in the building
The desk does not transfer the call and wait. They send help to the apartment and call the nurse or on-call clinician themselves, by whatever alert method your community uses. Then they come back to the caller:
“I’m sending staff to your mother’s apartment right now and I’m getting our nurse on this call. Please stay on the line with me.”
Keeping the caller on the line matters. If they hang up and you cannot reach them, the nurse loses the only person who saw what happened.
If the caller is with the resident somewhere else
Your nurse cannot assess someone who is in a car on the highway or at a daughter’s house two towns over. The only correct answer is emergency services:
“Based on what you’re describing, I need you to hang up and call 911 right now. Call me back at this number as soon as you have, and I will notify our nurse and your father’s care team immediately.”
Staff hesitate here because telling a family to call 911 feels like admitting the community cannot handle it. Train them out of that. Directing someone to 911 is the correct and defensible action, and it is the one your state surveyor will expect to see documented. Nobody at the front desk should ever be in the position of deciding whether a symptom is serious enough to skip 911.
The routine path: a message with a promised window
Most nurse requests are not emergencies. A daughter noticed Mom sounded foggy on the phone. A resident has a new ache and does not want to make a fuss. A son wants to know what the doctor said yesterday.
These are the calls that generate complaints, not because the concern was urgent, but because nobody told the family when they would hear back. “I’ll let the nurse know” sounds like a promise of a callback to the family and like an FYI to the nurse. Two people hang up with two different understandings, and neither is written down.
Fix it with a named window. Pick the windows that match your actual staffing, put them in writing, and have every person at the desk say one of them out loud on every call:
“Here’s what happens next. I’m sending this to our wellness nurse now with everything you told me. You’ll hear back from our team before the end of the day. If anything changes before then — trouble breathing, chest pain, a fall, or he can’t be woken up — call 911 first and then call us.”
Three things are doing work in that script. A named owner. A time the family can hold you to. And a safety net that tells the caller exactly what would change the answer, without asking your receptionist to evaluate symptoms.
Pick windows you can actually hit. A same-day promise you miss twice is worse than a next-morning promise you keep every time.
When there is no nurse in the building
Plenty of assisted living and memory care communities do not have a licensed nurse on site around the clock. Depending on the state and the license, a wellness director may work weekday business hours with an on-call arrangement covering nights and weekends. Independent living may have no nursing staff at all. Your script has to work on a Sunday at 9 p.m., not just on a Tuesday at 10 a.m.
The mistake is letting staff improvise an explanation of your staffing model to an anxious family member at night. They will either overpromise or sound like they are making excuses. Give them one sentence that is true in every setting:
“Our nurse isn’t in the building right now, but we have an on-call process for exactly this. I’m sending your concern to the nurse on call now, and someone from our team will call you back tonight. If anything gets worse in the meantime, call 911 and then call us.”
What that sentence never does is fill the gap with advice. The temptation is real: a caregiver or med tech is on shift, the family is worried, and it feels helpful to say “that’s probably just a urinary tract infection” or “give her some Tylenol and see how she does overnight.” Non-clinical staff giving that answer is the single largest risk in the whole workflow. It is practicing outside scope, it is undocumented, and it is what the family will quote back to you later.
The rule at the desk is simple and should be stated in training in these words: you collect facts and route them. You never interpret them. If a caller pushes for an opinion, the answer is “I’m not the right person to answer that, and I don’t want to give you wrong information. That’s exactly what I’m getting to the nurse.”
Then verify your own after-hours chain actually works. Who answers the main line at 9 p.m.? Who is the on-call nurse tonight, and is that list current? What number reaches them? What happens if they do not pick up in ten minutes — who is second? Where does the message get written so the morning team sees it? If you cannot answer all five from memory, neither can your evening associate.
The nurse requests that are not clinical
A significant share of “I need the nurse” calls are not nursing at all. Laundry went missing. Dad said nobody helped him shower. A family member wants a general update and does not know who else to ask for. “Nurse” has become the word for “someone in charge.”
Routing all of that to nursing burns the clinical hours you are already short on, and it trains families to treat the nurse as the service desk. The fix is one sentence after the intake questions:
“That helps. If this is about how he’s feeling or his care, I’ll get it to the nurse. If it’s about meals, laundry, billing, transportation, or activities, I can get it to the person who can fix it faster — which sounds closer?”
One caution. A complaint about missed care — no shower, no help to the bathroom, medication not given — is not purely a service issue. Route it to the department head and flag it to the nurse and your executive director. Those are the calls that become state complaints, and you want them documented from the first contact.
What gets written down
Notes like “daughter upset, wants nurse” and “told nurse” are the ones you will be reading back six weeks later when a family says nobody ever called them. They prove nothing and help nobody.
Every nurse request gets a log entry with these fields, in whatever system you already use:
- Date and time the call came in
- Caller name, relationship, and confirmed callback number
- Resident name and where the resident was
- The concern in the caller’s own words
- Emergency signs reported or explicitly denied
- What the staff member told the caller to do
- Who it was routed to, and the time it was routed
- The callback window that was promised
- Whether the callback happened, and when
The “explicitly denied” line is the one people skip and the one that matters most. A note reading “Daughter called 7:40 p.m., reports resident seemed more confused on the phone. Denies fall, chest pain, trouble breathing, or loss of consciousness. Routed to on-call nurse 7:45 p.m. Callback number confirmed. Told family to expect a call tonight and to dial 911 if condition worsens.” tells the next person exactly what was and was not asked.
Add one handoff rule: any nurse request not closed before shift change is documented in the system and named in the verbal handoff. Verbal alone does not count. A message passed at 2:55 p.m. to someone walking in at 3:00 disappears reliably.
Ask your privacy officer or counsel what belongs in call notes, who can see them, and how long you keep them. Do not let that question sit unanswered while the log grows.
The caller who has already called three times today
Someone calls at 9 a.m., again at noon, again at 4 p.m., angrier each time. The instinct at the desk is to get defensive, or to quietly hand over the nurse’s cell number to make the calls stop. Both make tomorrow worse.
A repeat caller is telling you the loop never closed. Either nobody called back, or somebody called back and the family did not understand what they were told. Treat the third call as a process failure, not a difficult family.
What staff say on that call:
“You’ve called three times today and that shouldn’t have been necessary. I’m pulling up what we’ve logged so far so you don’t have to start over. Then I’m escalating this to our director, and either she or the nurse will call you back by [specific time].”
Then actually escalate it. A second unreturned promise is how a phone call becomes a complaint to the state.
If a family needs more contact than your normal rhythm provides, build them a structured plan — a standing weekly call with the wellness director, a single named point of contact, a care conference — rather than handing out a direct cell number. The back-door workaround feels generous in the moment and produces undocumented clinical conversations at 11 p.m. that nobody else on your team knows happened.
Test it before a real call does
A pathway that exists only in a binder is not a pathway. Run four calls as drills with whoever actually answers the phone, including weekend and evening staff, and watch for the moment they hesitate:
- A resident calls from their apartment: “Can I talk to the nurse? My chest feels tight.” Does the associate escalate, or take a message?
- A daughter calls at 8:30 p.m.: “My mom sounded confused tonight. I need a nurse.” Does the associate know who is on call and what window to promise?
- A son calls: “I need the nurse. Dad says nobody helped him with his shower.” Does it reach both the department head and the ED?
- A family member pushes: “Just tell me, does that sound like an infection to you?” Does the associate decline cleanly, or guess?
Then pull last month’s nurse-request log and look at three numbers: how many calls came in after hours, how many were routed to the wrong place, and how many have no recorded callback. That last one is your real exposure.
Consistency at the front door is the hard part, because it depends on whoever happens to be at the desk. An AI receptionist can help there — it asks the same intake questions on every call, listens for the escalate-now language, and writes the same record every time, including at 2 a.m. What it does not do is make the clinical call. That decision belongs to your nurse, and the point of the whole pathway is getting it to them fast, with context, on the record.
JoyLiving builds AI voice tools for senior living: an AI receptionist that answers and routes front-desk calls, and check-in calls that reach residents and flag the ones who need a visit. See how it works at joyliving.ai.

Ana Avila is a writer who covers the day-to-day operations of senior living communities: how calls get answered, how resident requests get handled, how families stay informed, and how small teams keep up with all of it.
Her work for the JoyLiving Operator Library focuses on the practical side of running a community. She writes about front desk workflows, after-hours coverage, request tracking, check-in programs, family communication, staffing, and the places where AI tools can take repetitive work off a caregiver’s plate. Most of her articles come from the same starting point: a real problem an executive director or front desk lead is dealing with this week, and what has actually worked for other communities facing it.
Ana writes for people who are busy. Her guides are meant to be read in one sitting, put to use the same day, and shared with staff without translation. She avoids jargon, explains technology in plain terms, and is careful not to oversell what any tool, including AI, can do.
A consistent theme in her writing is that technology should support the relationships at the heart of senior living rather than replace them. The measure of a good system, in her view, is simple: does a resident get help faster, does a family member get a clearer answer, and does a caregiver get more time with the people they care for.



