An AI phone agent for the calls a senior living community can never afford to rush
The phone in a senior living community carries some of the hardest calls in any industry. An adult child dials the main line two days after a parent's fall, working through a decision they never wanted to make. A daughter calls at 9 p.m. because the hospital just said her mother cannot go home on Friday. A resident's son wants to know how his father is settling in. In between, the same line handles transportation requests, dining reservations, and billing questions — and when the sales director is walking a family through the memory-care wing, the next family's first call rings out. First calls in this industry rarely come twice.
ThunderPhone gives an independent living, assisted living, or memory-care community an AI phone agent that works in both directions: inbound coverage so every inquiry is answered warmly on the first ring, and outbound campaigns for the steady, patient follow-up that long family decision cycles require. It follows your instructions and searches your approved knowledge base without inventing community policy.
The agent does not make care decisions, and it is never configured to sound like it might. It never recommends a level of care, never discusses a current resident's condition with a caller — those calls route to your staff — and never quotes care-level pricing beyond what the community has chosen to publish. Anything clinical or urgent escalates to a person immediately. You define what it may say, what it must collect, and when it must hand the call to a human, and the agent executes those rules exactly.
What a senior living phone agent can handle
First-inquiry calls, answered warmly and without a script that sounds like one
The first call from a family is not a transaction — it is often the most vulnerable moment in the relationship. The agent answers immediately, in an unhurried voice, collects only what your team asks it to collect — the caller's name, who they are calling about, and the best way to reach them — and lets the caller tell their story. It can answer approved questions from your knowledge base, describe living options in the plain terms you wrote, and offer the one next step that matters: a scheduled tour or a callback from your advisor. It never pushes, never closes, and never characterizes what kind of care someone's parent needs — that conversation belongs to your team.
Tour scheduling through your calendar
When the agent is connected to a calendar or CRM through an HTTP API, an MCP server, or webhooks, it can offer real tour times and book one on the same call, then deliver a structured inquiry record — caller, prospective resident, timeline, preferred contact — to your sales system instead of a sticky note. Families on a compressed timeline, such as a hospital discharge, can be flagged by your rules for an immediate warm transfer or a priority callback.
Follow-up outreach that stays patient
Senior living decisions take as long as families need them to take, and the follow-up that keeps a community present through that window is exactly the work a busy sales office drops first. An outbound campaign can work your inquiry list with wording your team approved: a gentle check-in after a tour, an invitation to a family event, an offer to answer new questions. Because the campaign runs on your list, your prompt, and your cadence, the tone stays consistent — helpful, never pressuring — and every call produces a reviewable transcript. Voicemail detection can leave your configured message or retry later on the schedule you set. The community remains responsible for consent, caller identification, calling windows, and do-not-call handling for all outbound calls.
After-hours and weekend inquiry capture
Hospital discharge planning does not keep business hours, and neither do the moments when families finally decide to call. After hours, the agent answers instead of voicemail: it takes a complete inquiry, answers approved questions, books a tour into open slots, and — when a caller's situation is urgent by your definition — follows your configured escalation path to on-call staff. The family that calls at 9 p.m. gets a calm voice and a concrete next step instead of a beep.
Calls about a current resident — routed, never discussed
Families of current residents call the main line too: how is Dad doing, did Mom get her medication change, can someone check on her. The agent's rule here is absolute and simple: it never discusses a resident's condition, location, or care — it verifies nothing and reveals nothing. It identifies the caller, captures what they need, and routes the call: a transfer to the wellness director during staffed hours, or a structured, immediately delivered message to the right team otherwise. Anything the caller describes as urgent follows your emergency path without delay. Your staff, who know the resident and the family's disclosure permissions, have the actual conversation.
Admissions and move-in coordination
Between "yes" and move-in day sits a stack of coordination calls the agent can carry: scheduling the pre-admission assessment with your nurse — the assessment itself is always performed by your licensed staff, never by the agent — walking families through the move-in checklist from your approved documents, confirming what paperwork to bring, and answering move-in-day logistics. Each call ends as a structured record, so your admissions coordinator starts the morning with a clean queue instead of a voicemail box.
Pricing and availability — only what you have made public
Cost is often the question families are most anxious to ask, and the agent answers it honestly within a hard boundary: it shares exactly the pricing the community has configured as public — base rates, what is included, how care levels are generally structured — and nothing more. Care-level pricing that depends on an assessment routes to your advisor, stated plainly rather than dodged. Availability and waitlist questions work the same way: the agent answers from what your team keeps current in the knowledge base or a connected system, and takes waitlist requests as structured tasks for staff review.
Respite and short-term stays
Respite inquiries are frequently a caregiver's first contact with a community, and they arrive tired. The agent can explain your respite program from approved material — minimum stays, what is furnished, how booking works — collect the details your program requires, and route the request to your team. A well-handled respite call is often the beginning of a longer relationship, which is exactly why it should never land in voicemail.
Everyday resident and family logistics
The same line carries the community's daily operations: transportation requests, private-dining and event reservations, maintenance requests from residents or their families, activity-calendar questions, and billing questions that route to the business office. The agent handles each from your instructions — booking through a connected system where you allow it, or filing a structured task where a person should act — keeping the front desk free for the people standing in front of it.
Multilingual family communication
ThunderPhone supports 47 voice languages across 123 voices. Set a primary language and additional languages for your resident families, and the agent can switch mid-call when a caller changes to one of the selected languages — no separate line, no waiting for the one staff member who speaks it. The same warmth, privacy, and escalation rules apply in every configured language.
Sample senior living call flow
Agent: Thank you for calling Willow Creek Senior Living. How can I help you today?
Caller: I'm calling about my mom. She's in the hospital right now and they're telling us she can't live alone anymore. I honestly don't know where to start.
Agent: I'm glad you called, and please take your time. Can I get your name, and your mother's first name, so I know who I'm speaking with?
Caller: I'm David Chen. My mom is Ruth.
Agent: Thank you, David. When is the hospital expecting Ruth to be discharged?
Caller: They said probably Friday.
Agent: Then let's make sure the right person talks with you quickly. Our advisor, Maria, meets with families in exactly this situation, and I can schedule a tour or a phone conversation as soon as tomorrow morning. Which would be more helpful?
Caller: A call tomorrow morning would be great. Can you tell me roughly what it costs?
Agent: Of course. I can share our published starting rate for assisted living. The full monthly cost depends on a care assessment our nurse does with Ruth, so Maria will walk you through exactly how that works tomorrow — no surprises.
If a caller asks about a current resident's wellbeing, the agent shares nothing and routes the call to staff. If a caller describes anything urgent or clinical, it immediately follows the community's configured escalation path. Every branch, including the exact wording of the pricing answer, comes from the community's script.
Features that matter in a senior living community
GDPR and HIPAA compliance posture — and your configuration responsibility
ThunderPhone's public compliance posture is GDPR and HIPAA compliant. That posture does not make any particular community workflow compliant by itself. The community decides and configures: what caller information the agent collects, whether calls are recorded and what notice callers hear, how long transcripts are retained, which integrations receive resident or prospect information, and who can access call data. The never-discuss-a-resident rule should be written into the prompt explicitly and reviewed by whoever owns privacy compliance — in a memory-care setting especially, treat that review as non-optional.
CRM, calendar, and community-system connections
Agents can use connected apps, HTTP APIs, or MCP tools during a call — check tour availability, create an inquiry record, book an assessment, file a maintenance ticket. Webhook deliveries are HMAC-SHA256-signed and retried automatically, so a briefly unavailable endpoint does not lose a family's inquiry.
Knowledge grounded in your documents
Attach your community fact sheet, published rate sheet, respite-program description, move-in checklist, and FAQ — as text or PDF/DOCX uploads (up to 5 MB per text file and 50 MB per PDF or DOCX), or imported directly from a page on your website. The agent searches those documents mid-call instead of improvising, and each agent uses only the documents you scope to it.
Your numbers, your telephony
Bring the community's existing numbers through a supported VoIP connection or SIP configuration; verified numbers handle inbound and outbound calling, so families keep dialing the number they know. A web voice widget can put the same agent on your website, where many families prefer to start.
Human handoff built for sensitive moments
Cold transfers route a caller immediately. Warm transfers, available on eligible production VoIP or SIP numbers that can place an outbound leg, are the right shape for this vertical: the caller waits while the agent privately briefs your advisor or on-call staff member, and the call connects only when the recipient accepts — so a family in a hard moment never retells their story to a cold pickup.
Testing before a family ever hears it
Rehearse the calls that worry you. Run AI-caller simulations: a tearful first inquiry, a caller pressing for a resident's condition, a family demanding a care-level price, an urgent after-hours report. Simulations produce transcripts and grading against your criteria, and graded scenarios can be kept as a regression suite so a prompt change never quietly weakens the privacy rule or the escalation script. Every production call leaves a transcript — and a recording when recording is enabled — that the team can review.
Guardrails the community controls
- No care recommendations, ever. The agent never suggests a level of care or characterizes what a prospective resident needs. Assessments and care conversations belong to licensed staff.
- A resident's condition is never discussed. Calls about a current resident are routed to staff with a structured message — the agent verifies nothing and reveals nothing, regardless of who is asking.
- Pricing stays inside the published line. The agent quotes only what the community configured as public and routes assessment-dependent pricing to an advisor.
- Clinical and urgent calls escalate immediately. The community writes the triggers and the paths; the agent executes them verbatim and never downgrades a call its rules flag.
- Warm, never salesy. Follow-up cadence, wording, and tone come from your approved scripts, and transcripts make every conversation reviewable.
What would this cost each month?
Suppose a community handles 500 AI-assisted calls per month, averaging 5 minutes each — family inquiries run long, and they should:
500 calls × 5 minutes = 2,500 minutes per month
- Spark:
2,500 × $0.02 = $50/month - Bolt:
2,500 × $0.05 = $125/month - Storm:
2,500 × $0.09 = $225/month
That is illustrative base engine usage, not a quote — pay as you go, with no subscription. Premium voice or language paths can add up to 3¢ per minute, and phone-number or carrier charges depend on the telephony setup. Hold time bills a flat 2¢ per minute; voicemail and phone-menu minutes bill at the engine rate. Optional add-ons such as verbal acknowledgements, call supervision, and long prompts carry their own published surcharges. The agent builder shows the current all-in rate before calls are placed.
Frequently asked questions
Can a ThunderPhone agent schedule tours of our community?
Yes, when it is connected to a calendar or CRM that permits the action, through an HTTP API, an MCP server, or a webhook into your systems. The agent collects the inquiry details your team specifies, offers real tour times, books or reschedules, and delivers a structured inquiry record alongside the booking.
Is ThunderPhone HIPAA compliant for a senior living community?
ThunderPhone's public posture is GDPR and HIPAA compliant. The community remains responsible for configuring a compliant workflow: what information the agent collects, recording and notice settings, retention, which integrations receive resident or prospect data, and who can access call data. Review the configuration — including the resident-privacy rules — with your compliance owner before launch.
Will it tell a family member how their parent is doing?
No. The agent never discusses a current resident's condition, care, or whereabouts with any caller. It takes the caller's details and routes the call to your staff — by transfer when someone is available, or as an immediately delivered structured message otherwise — because your team know the resident and the family's disclosure permissions.
Can it answer pricing questions?
It answers with exactly the pricing the community has configured as public and routes anything assessment-dependent to your advisor. It never estimates a care-level cost, because that number depends on a clinical assessment your staff perform.
What happens if a caller reports something urgent?
The community writes the triggers and the response — a warm transfer to on-call staff, an approved emergency instruction, or an immediate webhook alert to the team — and the agent follows that path the moment a trigger is met. It never assesses urgency on its own and never downgrades a call its rules flag.
Can one agent speak with families in multiple languages?
Yes. Configure a primary language and additional languages from the 47 supported, and the agent can switch mid-call when a caller changes language, provided the selected voice supports the configured set. The same privacy and escalation rules apply in every language.
How do we make sure it sounds right before families hear it?
Test in the browser first, then run AI-caller simulations of the hard scenarios — a distressed first inquiry, a caller pushing for information about a resident, an urgent after-hours call. Simulated calls are graded against your criteria and can be re-run as a regression suite whenever the prompt or knowledge base changes, so the tone and the guardrails hold together.