A daughter calls at 9:40 p.m. She says her mother sounded confused on the phone tonight, more than usual, and she wants someone to look in on her. The business office closed six hours ago. Whoever picks up that call has about ninety seconds to decide whether this is a note for the morning, a check-in before the end of the shift, a call to the on-call nurse, or a 911 call.
Most after-hours problems in senior living are not answering problems. They are deciding problems. The phone gets picked up and then the call sits, because the person holding it does not know what they are allowed to decide. This is a playbook for making that decision the same way every night, no matter who is on the floor.
First, decide who actually answers the line
Communities usually cover after hours in one of four ways. Each one works, and each one fails in a specific, predictable place. Pick yours on purpose and then build around its weakness.
- A caregiver on the floor. Knows the residents, knows the building. Fails when they are in an apartment with a resident, gloves on, and the phone rings. The call is missed or answered badly, and the documentation gets written from memory two hours later.
- The on-call manager’s cell phone. Real authority, real context. Fails on volume and on sleep. When every routine question routes to one person’s phone, they stop answering the routine ones, and the urgent one arrives in the same silence.
- An answering service. Fast pickup, always staffed. Fails on context. They do not know which resident has fallen twice this month, so everything comes through at the same flat priority, and the morning team spends an hour translating generic messages into real tasks.
- An AI receptionist. Answers every call and never queues. Fails if you have not written your escalation rules down, because it can only run the rules you give it.
JoyLiving’s AI receptionist sits in this slot: it answers 24/7, identifies who is calling and how urgent the call is, answers routine questions from your community’s own information, takes messages and opens tickets, escalates according to the rules you configure, and logs a summary of every call. It does not replace your escalation rules or your team’s judgment. It runs the rules you already wrote, which is exactly why the rest of this playbook matters more than the choice of who answers.
Ask two questions, not one
Most after-hours training teaches one question: is this an emergency? That question is too blunt for senior living, because it only looks at the issue and never at the person.
Split it in two. Call urgency asks: does this specific issue require action now? Resident vulnerability asks: is this resident more likely to be harmed, frightened, or destabilized if it waits?
They come apart constantly. A broken TV remote is not urgent. If the resident uses the TV to settle at night and has called three times this week when it stopped working, waiting until morning produces a distressed resident and four more calls. A question about breakfast time is not urgent either, unless the person asking has memory loss and is awake and worried at 3 a.m., in which case the answer they need is reassurance, not a time.
Vulnerability is not a mystery. It comes from what your team already knows: recent falls, a recent change in medication or care level, new confusion, nighttime anxiety or sundowning, a recent hospitalization, a recent death in the family, a resident who lives alone with no family nearby. Keep a short list of the residents who currently sit high on that scale and make it available to whoever is covering the phone. Ten lines per resident is plenty: apartment number, mobility, fall notes, nighttime pattern, recent care change, approved contacts, and the one instruction that matters after hours (“if she calls more than twice in an hour, notify the shift lead”).
The triage grid
Put the two questions on a grid and you get four cells. Every after-hours call lands in one of them. Post this where the phone is answered.
- Low urgency, low vulnerability — log and schedule. A resident asks what time the bus leaves for the Thursday outing. A family member wants to confirm the care conference. A dripping faucet in a second bedroom. Take the details, tell the caller when it will be handled, put it in the overnight log for the right department. Nobody gets woken up.
- Low urgency, high vulnerability — reassure, document, and check in before the shift ends. A resident with recent nighttime anxiety calls at 1 a.m. to ask whether her daughter is coming tomorrow. A resident who fell last month calls to say his room is cold. The issue can wait. The person cannot be left alone with it. Stay on the line long enough to settle them, then put eyes on them before the shift changes and write down that you did.
- High urgency, low vulnerability — route now to the right person, no escalation needed. Water coming from under a door. A failed door lock or a fire panel trouble light. A resident locked out of her apartment at 11 p.m. These need someone moving in the next few minutes, but they do not need a nurse and they do not need the executive director.
- High urgency, high vulnerability — escalate immediately and document every step. A resident with a known fall history says she is on the floor. A family member says her father is slurring his words. A resident with a recent medication change reports chest tightness. Someone goes to the apartment now, the on-call clinical role is contacted now, and the log gets written as it happens, not afterward.
The grid also gives you a better way to review a call that went wrong. Instead of “we need better communication,” the question becomes specific: did we misread the urgency, the vulnerability, or both? That is a question a team can actually answer and fix.
Some signals move a call up a cell regardless of the topic. Train your team to listen for them: the caller says they do not feel safe; the caller sounds confused, breathless, or panicked; a sudden change from how that person normally sounds; the caller cannot say where they are; any mention of a fall, chest pain, dizziness, or new weakness; a third call about the same thing; a family member saying “she didn’t sound like herself.”
Define authority, not just departments
Routing by department gets you halfway. Maintenance issues go to maintenance, care concerns go to care staff. But the person holding the phone at 1 a.m. does not only need to know which department owns the topic. They need to know who is allowed to make the next decision.
Can the overnight caregiver promise a family member a callback? Can they decide not to call 911? Can they move a resident to a guest apartment because a pipe burst? If nobody has answered those questions in advance, staff either freeze or escalate everything. Hesitation creates risk; over-escalation burns out your on-call people until they stop picking up.
Write four levels and name the actual roles in your building.
- Level 1 — whoever answers. Verify the caller against the resident’s approved contacts, capture the details, answer approved questions from published community information, resolve comfort items within policy, create the ticket, and tell the caller what happens next and when. May not give out health information, may not promise a care change, may not decide that a safety concern can wait.
- Level 2 — on-duty shift lead. Dispatch staff to an apartment, order a same-shift wellness check, resolve routine comfort and environmental issues, decide that a non-clinical item waits until morning, and decide to move the call up to Level 3.
- Level 3 — on-call nurse or clinical lead. Anything involving a change in condition, a medication question, a fall with or without injury, new confusion, pain, or a resident who cannot safely transfer. This level also decides whether the resident goes to the emergency department, and notifies the family of a care change.
- Level 4 — executive director or administrator. Death of a resident, a resident who cannot be located, police or fire on site, a building-wide utility failure, a serious family complaint, allegation of abuse or neglect, media contact, or any event your state requires you to report.
Then write the short list that sits outside all four levels: call 911 first, then start the ladder. Unresponsiveness, trouble breathing, chest pain, suspected stroke, active bleeding, a fall with obvious injury or head strike, a fire or smoke, a resident who has left the building and cannot be found. Nobody waits for a callback from a manager to dial 911. Say that in exactly those words, in writing, and say it again in every orientation. Reporting requirements for incidents like these vary by state, so check your state’s assisted living regulations and put those timelines into the Level 4 list.
On-call rules that hold up at 2 a.m.
An on-call list is not a policy. A policy says what “on call” obligates a person to do, how fast, and what happens when they do not answer. Use this as a checklist against your current document.
- Name the on-call role for each night on a published schedule, at least two weeks out, with a phone number next to the name. Not “the manager.” A name.
- Set a response window per level and write it in minutes. For example: Level 3 answers within 10 minutes, Level 4 within 20. Pick numbers your team can actually hit and then hold to them.
- Name a second on-call for every shift. One person with one phone is not coverage; it is a single point of failure with a battery.
- Write the no-answer rule: call once, wait the window, call again, then call the second on-call, then call the executive director. Do not leave the sequence to judgment at 2 a.m.
- State that the on-call person acknowledges by voice, not by text. A text can be sent half-asleep and forgotten.
- Require the person coming on call to confirm they have the phone, that it is charged, that it is not on silent, and that they have coverage for the whole window.
- Define what on-call does not cover, so the floor knows what they own: routine maintenance, dining requests, activity questions, billing, tours.
- Log every escalation with the time it was made and the time it was answered. Review the gaps monthly. A response window nobody measures is a wish.
Tell families the rules at move-in, before they need them
Almost every angry after-hours family call is really a mismatch of expectations set months earlier. Cover after-hours contact during move-in, in writing, in the same packet as the lease and the care agreement. Say four things plainly.
- The number to call at night is the community’s main line. It is answered around the clock, and there is no separate emergency number to memorize.
- What you will do the same night: check on their family member, handle safety and comfort issues, and contact them if there is a change in condition or an emergency.
- What waits for business hours: care plan discussions, billing, scheduling, staffing questions, and anything needing a department director.
- Who you may share information with. Confirm which contacts are listed and approved for the resident, and explain that the overnight team will confirm identity before discussing anything. Update that list whenever the family changes.
Give the overnight team approved language so they are never improvising about what they can share. When a caller asks for details the person answering is not cleared to give, “I can’t tell you anything” is the wrong answer. This is better:
“I understand why you’re worried, and I’m glad you called. I’m not the right person to go through her care details, so let me confirm what I’m able to share and get this to the nurse on call tonight. What I can do right now is have someone look in on her and call you back to confirm. Is this the best number?”
And when something genuinely can wait, do not say “that will have to wait until morning.” Say this:
“I’m logging this now so the morning team has it first thing, and I’ll put your name and number on it. This doesn’t look like an immediate safety concern, so we’ll handle it during the day. If anything changes tonight, or you feel like something isn’t right, call this same number back right away.”
The overnight log and the morning handoff
A note that says “resident requested help with heat” is not documentation. It tells the morning team that something happened and nothing more. Every after-hours call that creates work should capture the same fields, every time.
- Time of the call and who answered it.
- Caller name, relationship, and callback number.
- Resident name and apartment.
- What was reported, in the caller’s words where it matters.
- Grid cell assigned: urgency and vulnerability.
- What was done, and at what time.
- Who it was escalated to, at what time, and when they responded.
- Owner of the next action, and the deadline for it.
- Status: resolved on the call, staff dispatched, escalated to clinical, escalated to leadership, family callback owed, queued for morning, 911 called.
- Whether the caller was told what happens next.
Filled in properly, the same entry reads: “Apartment 214 reported no heat at 10:18 p.m. Room cold, no health complaint, low urgency and low vulnerability. Night lead brought blankets at 10:35 p.m. and confirmed resident comfortable. Maintenance ticket opened. Owner: maintenance lead, by 9 a.m. Status: queued for morning. Resident told maintenance will come before 9.”
That log also lets the second person to take a call pick up where the first one left off, which is the difference between a family calming down and a family escalating:
“Yes, I can see your call from 12:03. It went to the on-duty team and a caregiver checked on your father at 12:20. Let me tell you exactly what they found, and then I’ll get you an update on the piece that’s still open.”
Then make the morning handoff a report, not a pile of messages. Sort overnight items into six buckets in this order, and put the open ones first: needs leadership review; needs clinical or wellness follow-up; family callback owed; maintenance or environmental; routine department task; pattern to watch. Whoever runs the morning stand-up reads the open items out loud and assigns each one a name and a time. Items with no owner and no deadline do not leave the meeting.
The last bucket earns its place over time. One thermostat complaint is nothing. Five from the same hallway is a building problem. One reassurance call is normal; the same resident calling at 2 a.m. four nights running is a care plan conversation, not a nuisance.
Test the chain before it is tested for you
Every part of this fails silently. The on-call phone goes to a full voicemail box. The answering service has last quarter’s escalation list. The new night caregiver has never been told she is allowed to call 911 without permission. You will not find out on a quiet Tuesday. You will find out on the worst night of the year.
Test it on a schedule instead.
- Once a month, at a random hour after 9 p.m., call your own main line from an outside phone. Time how long it takes to be answered and whether the greeting is right.
- Once a month, run one live escalation drill to the on-call role. Say clearly that it is a drill. Record the time you called and the time they answered, and compare it to your published window.
- Once a quarter, run a tabletop on three scenarios with the overnight team: a resident found on the floor, a family member demanding health information they are not approved for, and a resident who cannot be located. Ask each person what they are allowed to decide. Where two people answer differently, your policy is unclear.
- Once a quarter, pull ten overnight log entries at random and check them against the field list above. Missing fields tell you which part of the process is too slow to use at 2 a.m.
- After any real escalation, do a five-minute review the same week. One question only: did we read the urgency right, the vulnerability right, or neither?
Keep the whole system simple enough that following it is easier than working around it. If your night lead has to open three systems and fill in fourteen fields to log a cold room, they will text someone instead and the record will not exist. Ask them directly: at 2 a.m., while you are busy, does this still make sense? If the answer is no, cut steps until it does.
None of this makes the 9:40 p.m. call easier to hear. It makes the next ninety seconds the same every time, no matter who is holding the phone. That is what families are actually asking for when they call at night, and it is the part you can build.
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.



