Almost every automation I have written up on this site rests on an assumption so quiet that it never gets stated: the person who contacts the business is the person who buys, and they have one timeline. A missed call is one caller. An abandoned quote form is one household. A lapsed policy has one named insured. Home care breaks that assumption in three places at once, and it is the reason agencies keep installing generic speed-to-lead automation and getting a fraction of the result that a plumber gets from the same build.
Here is what actually arrives in a home care agency's inbox. A woman fills in the contact form at 11pm. She is not the client. Her father is the client, and he has not agreed to any of this — she is at the kitchen table with a hospital discharge summary trying to work out whether he can go home on Thursday. Twenty minutes later a second inquiry arrives from a man planning six months ahead for his mother, no deadline, no crisis, and a strong chance he talks to five agencies before doing anything. And in the morning a hospital case manager emails a referral for a patient who needs to be placed by Friday, with two other agencies copied in, effectively.
Three inquiries, one form, one inbox, and three completely different jobs. Most agencies run all three through the same follow-up sequence, and I would argue that is the single largest structural leak in the vertical. As Gideon Wafula, AI Automation Engineer, I want to pull this one apart carefully, because the compliance and dignity constraints here are tighter than anything I have covered, and the naive build is not just weak, it is actively harmful.
The dominant decision-maker in home care is the adult child. Industry marketing analysis in 2026 keeps landing on the same point: agencies market as though the senior is the audience, while the research, the shortlisting, the emotional processing and usually the payment are being handled by a son or daughter. Some analysts break the audience into three distinct personas — the adult child researching, the senior weighing their own autonomy, and the professional referral source routing a patient — and note that agencies building separate tracks for each convert better than those treating "families" as one persona.
For an automation engineer this is not a copywriting nuance, it is a data model requirement. Your table needs an enquirer record and a care recipient record as separate entities from the first touch, with the relationship between them stored explicitly and left null when unknown rather than guessed. Every outbound message goes to the enquirer. Consent for SMS belongs to the enquirer. And there is a failure mode with no equivalent anywhere else on this site: an automated text that addresses the senior directly, or that lands on a phone the senior answers, can disclose to a parent that their children are arranging care for them before that conversation has happened. That is not a bad customer experience. That is a genuine harm, and it is the reason I hard-code outbound contact to the enquirer's stated number and refuse to fall back to any other number in the record.
An acute inquiry and a planning inquiry look identical on a web form and need opposite treatment. The acute one is attached to a hospital discharge, and discharge planning runs on a brutally short window — the case managers doing this work are typically operating inside a twenty-four to seventy-two hour placement horizon while carrying a full caseload of other discharges the same week. If you reply to that inquiry in four hours you have not been slow, you have been absent; the decision was made without you.
The planning inquiry is the opposite. It has no deadline, the family is comparing options, and the risk is not slowness but pressure. Hit that person with a same-day "are you ready to book" cadence and you read as a business trying to sell a stressful decision to someone who has explicitly told you they are not ready. They go quiet, and the record sits in the CRM as a dead lead when it was actually a warm one you burned.
So the first real branch in the workflow is not a scoring model, it is a classification: does this inquiry have a hard date attached, or does it not? Everything downstream forks there.
Nobody buys home care from a web form. The transaction that matters is the in-home assessment or care consultation, where a nurse or care manager sits in the living room, sees the stairs and the medication list and the state of the kitchen, and builds a plan. The pipeline agencies actually run looks something like: new inquiry, initial contact made, assessment scheduled, assessment completed, agreement sent, signed and active, or on hold and lost. Two of those stages are where the automation lives, and neither of them is "sale". Your metric is inquiry-to-assessment-booked, and then assessment-booked-to-assessment-held. If you measure inquiry-to-signed you will never be able to tell whether your problem is intake or your consultation.
Before building anything, pull twelve months of inquiries out of whatever system holds them — an agency CRM, a shared inbox, a spreadsheet, in a lot of agencies genuinely a spreadsheet — and compute four things.
Median time from inquiry to first human contact, split by hour of arrival. Median, not average; one weekend inquiry answered on Tuesday will drag an average into meaninglessness. Split it into staffed hours and unstaffed hours, because those are two different problems with two different fixes. The lead-nurture literature in this vertical is consistent that the odds of a meaningful conversation with a decision-maker fall away sharply within the first hour, and one widely repeated figure holds that responding inside an hour makes a substantive conversation with a decision-maker roughly seven times more likely than waiting even an hour longer. I would treat the exact multiple as directional rather than gospel — but the direction is not in dispute, and you can measure your own version of it in an afternoon.
Inquiry-to-assessment-booked rate, split by source. Website form, inbound phone, referral partner, and paid directories will not behave alike, and a single blended rate hides which channel is actually broken.
Assessment show rate. An assessment booked three weeks out for a planning family is a different animal from one booked for tomorrow afternoon, and if a meaningful share of scheduled assessments never happen, your first build is confirmation and reminders, not lead response.
Referral-partner turnaround. For every referral from a case manager or discharge planner, how long until someone at your agency gave that partner a yes or a no? Not until you contacted the family — until the partner got an answer. Referral sources have less time than they had two years ago, and the agencies growing right now are the ones whose name surfaces first when a partner has ninety seconds to place someone. Note too that a meaningful share of home health referrals get declined for service-mismatch reasons; that is not a failure, but it needs to be a fast, clearly communicated decline rather than a slow silence.
Then, as always, call twenty families who inquired and never booked an assessment. You are trying to learn whether the constraint is response speed, price, availability of caregivers in their postcode, or the fact that dad refused. Only the first two are automation problems. If it is caregiver availability, you have a recruiting problem wearing an intake costume, and no workflow will touch it.
Six steps in n8n, sitting on whatever the agency uses — WellSky, AlayaCare, Axiscare, a home care CRM, or in smaller agencies a shared inbox and a calendar.
Consolidate website form, tracked phone line, info@ inbox, and referral-partner email into a single staged table. Every row carries: enquirer name and contact details, relationship to the care recipient, care recipient first name only, geography, a free-text situation description, arrival timestamp, source, and an explicit acuity field that starts null. Anything you do not know stays null. In this vertical especially, an inferred field that turns out to be wrong shows up in a message to a frightened family member, and there is no recovering from that with a follow-up apology.
This is the one place I let a language model do interpretive work. It reads the free-text description and classifies into three buckets: acute (a discharge date, a fall, a hospital or rehab stay, a caregiver who has just quit, the words "this week"), planning (no date, exploratory language, comparison shopping), and unclear. Unclear routes to a human — and I set the threshold deliberately low, so borderline cases land in the unclear bucket rather than being confidently mis-sorted. Misclassifying a planning inquiry as acute is mildly annoying. Misclassifying an acute discharge as planning loses a client who needed help on Thursday.
The acute branch does almost nothing clever. Within a couple of minutes it sends one short message to the enquirer acknowledging the specific situation they described in their own words, confirming the agency covers their area, and offering two named assessment windows in the next forty-eight hours behind a one-tap booking link that reads a real calendar. Simultaneously it pages the on-call intake person. The automation's entire job on this path is to hold the family's attention for the fifteen minutes it takes a human to pick up the phone. It is not a nurture sequence and it must never become one.
The planning branch is where agencies most often over-automate. What works is a short acknowledgement the same day that answers the practical questions the family is actually holding — do you serve this area, what does an assessment involve, is there a cost to it — followed by a small number of spaced, useful touches over several weeks. Four touches over three to four weeks with the ask arriving later rather than sooner is the shape the funnel benchmarking in this space converges on, and it is roughly what I build. Every message ends in a booking link and a plain sentence saying it is fine to reply "not yet". Any reply of any kind stops the sequence and routes to a person.
Referral inbound gets its own workflow with a different goal. The moment a referral arrives it is logged, the partner receives an immediate acknowledgement confirming receipt and naming who is handling it, and a named human is paged with an SLA on giving that partner an accept-or-decline answer. The workflow tracks time-to-answer per partner and reports it weekly. It does not send marketing to case managers, it does not enrol them in sequences, and it does not attempt to be clever. The point of automating this channel is to make the agency look reliable to a professional who is measured on throughput.
Suppression evaluated at send time rather than at selection: existing clients and their families, active assessments already scheduled, anyone contacted by a human in the last twenty-four hours, opt-outs, duplicate inquiries from the same household through different channels (extremely common, and a family getting three parallel sequences is a memorable failure), out-of-area postcodes, deceased care recipients, and any record a care manager has flagged.
The model's remit is narrow and I keep it that way. It classifies acuity, and it drafts short scheduling copy in a warm register. It is deterministically blocked from producing any hourly rate, package price, minimum-hours figure, funding or insurance eligibility statement, Medicaid or local-authority coverage claim, availability guarantee, clinical assessment of the situation described, or any reassurance about what care the person will qualify for. Every one of those is either a regulated statement, a commercial commitment, or a clinical judgement. Drafts containing a currency figure, an eligibility word, or a clinical term are rejected before send and fall back to an approved template that says a care manager will call. That validation step is not paranoia; families in this situation read messages very closely and quote them back to you months later.
US agencies are in TCPA territory for SMS: documented consent from the enquirer, immediate honouring of opt-out, and messages inside 8am to 9pm local time. If the agency touches protected health information — and a referral from a discharge planner definitely does — HIPAA applies to what the workflow reads as well as what it sends, so the staged table should hold the minimum necessary and message bodies should carry no clinical detail whatsoever. In the UK and EU, health and care information is special category data under UK GDPR and GDPR, which means a DPIA before you switch anything on, and a clear separation between responding to an inbound inquiry and adding someone to a marketing list. The lawful basis for one is not the lawful basis for the other.
There is also a non-legal boundary worth naming. A family arranging care for a parent is often doing so at the worst week of their year. Urgency language that works fine for a roofing quote — limited slots, act now, this offer expires — is grotesque here and will cost the agency the client and the review. I write the copy for this vertical assuming it will be read aloud to a sibling.
Running cost lands around 40 to 150 USD per month for platform, model usage and messaging. That is not the interesting number. The interesting number is that a single retained home care client typically represents tens of thousands in lifetime revenue, so the build pays for itself on a single recovered inquiry, and the real expense is the one-time work: integrating the scheduling or agency management system, cleaning up how inquiries are currently captured, and standing up the human escalation path so the automation always has somewhere to hand off to.
Four metrics, each baselined before you switch anything on. Median time to first human contact, split staffed and unstaffed hours — this is the number the build exists to move. Inquiry-to-assessment-booked rate by acuity bucket, because a single blended figure will hide the acute path working and the planning path failing, or the reverse. Referral-partner time-to-answer, tracked per partner and reviewed monthly with the person who owns those relationships. And opt-out and complaint rate as a circuit breaker that pauses the workflow automatically rather than waiting for someone to notice.
Faster, better-sorted intake delivers more families to your assessment. It does not improve the assessment, and it cannot conjure a caregiver in a postcode where you have none. If your inquiry-to-assessment rate is healthy and your assessment-to-signed rate is poor, this build will simply help more people decline you, more promptly. And if the constraint is staffing — which in home care it very often is — then the most useful thing automation does here is surface that fact faster and with numbers attached, which is worth something, but is not the thing you were hoping to buy.
The pattern itself ports further than you might expect. Any service where a third party arranges care or purchase on behalf of the recipient has this same split-identity, split-clock structure: assisted living placement, paediatric therapy services, special educational needs provision, disability support, addiction treatment admissions, and to a lesser degree veterinary end-of-life care. If you have read the law firm intake teardown, you will recognise the shape — high emotional stakes, a regulated ceiling on what a model may say, and a conversion event that is a conversation rather than a checkout.
Gideon Wafula builds custom AI automation systems, n8n, WhatsApp, Voice AI, and more.
See Services →