Care home CRM automation from first enquiry to move-in
Families looking for a care home are often in a hurry and under stress, and their enquiry may come by phone, web form, a directory listing or a hospital discharge team. We connect every source to one senior living CRM pipeline, book tours quickly, send gentle follow-ups after each step and report which sources lead to admissions. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.
The problem
Why care homes lose family enquiries
A family enquiry often arrives at the worst moment for the home: during a medication round, a handover or an inspection. The manager means to call back, but by the next day the family has toured two other homes.
Without one pipeline, nobody knows how many enquiries came in last month, how many toured, which were waiting on a funding decision or a needs assessment, or which directories and referrers lead to move-ins. Occupancy planning becomes guesswork.
What we build
What our care home CRM automation includes
Every source in one pipeline
Calls, web forms, directory listings, email and hospital or social worker referrals flow into one CRM.
Stages that match admissions
Enquiry, tour booked, toured, assessment, funding confirmed, offer, move-in date, set to how the home works.
Quick tour booking
Families get an acknowledgement and tour options within minutes, in person or by video.
Gentle follow-ups
A thank-you after the tour and a check-in a few days later, stopping the moment the family replies or decides.
Waiting list and vacancies
Families waiting for a room are kept on a list and contacted when a suitable room is free.
Occupancy report
A weekly report of enquiries, tours, assessments and move-ins by source.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Enquiry arrives
A call, form, directory lead or referral creates or updates a contact.
-
02
Automated
Tour offered
The family gets an acknowledgement and tour options within minutes.
-
03
Automated
Follow-ups
Thank-you and check-in messages go out after the tour, with stop rules.
-
04
Office or senior review
Admissions lead calls
The manager or admissions lead calls the family and records the outcome.
-
05
Registered manager or nurse decides
Needs assessment
Whether the home can meet the person's needs is decided by the registered manager or clinical lead.
How it behaves
How the admissions pipeline behaves
What the family sees
- A quick, warm acknowledgement and tour options
- A call from the manager or admissions lead
- A thank-you after the tour and one check-in, no pressure
What staff see
- One board with every enquiry and its stage
- Call tasks with due dates
- A weekly occupancy report by source
What the automation does
- Captures and de-duplicates enquiries
- Books tours and sends follow-ups with stop rules
- Keeps the waiting list current
Edge cases and fallbacks
- Urgent discharge referral
- Flagged to the admissions lead at once for a same-day call.
- Family enquires about two homes in a group
- One contact, routed to the home that fits, with both managers informed.
- Enquiry describes an emergency
- No automated reply beyond directing them to emergency services; staff alerted.
- CRM outage
- Enquiries are queued and retried, and the office gets an alert.
Architecture
A care home admissions pipeline at a glance.
- Input
- Logic and services
- Data
- Output
- People
How it flows
- 1 Enquiries arrive from family calls, web forms, directory listings and hospital or social care referrals.
- 2 n8n captures each one, removes duplicates and creates the contact and deal in the CRM.
- 3 Families get tour options straight away, and the admissions lead gets a call task.
- 4 A weekly report shows enquiries, tours, assessments and move-ins by source.
Project planner
How the project runs, phase by phase.
Care home CRM & admissions pipeline project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Enquiry sources, current tracking, admissions steps, funding routes and reporting needs.
-
02
Design
2 to 3 days
Stages, tour booking rules, follow-up wording, consent and duplicate rules.
-
03
Build
1 to 2 weeks
Source connections, pipeline, tour booking, follow-ups and report.
-
04
Shadow run
About 1 week
Enquiries flow into the CRM while the team keeps its old notebook, and we compare.
-
05
Launch
1 to 2 days
Switch over and train the manager and office team.
-
06
Support
Ongoing
New sources, stage changes and report tweaks.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Time with the registered manager and office team, wording, data flows and a written specification.
$200 – $400
-
Build
The n8n workflow, rules, drafting step where useful, logging and error handling.
$500 – $1,300
-
Integrations
Care platform, rota or CRM access, messaging and alert channels.
$150 – $400
-
Testing and shadow run
Acceptance tests and a parallel run while the team keeps its current process.
$100 – $250
-
Launch and training
Go-live, short staff training and a run book.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. CRM licences, messaging and n8n are billed to you directly. Groups with several homes may need a second workflow for routing.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- CRM licence: Your CRM vendor's own plan (WelcomeHome, Aline, HubSpot or the CRM you already use).
- n8n: Free self-hosted Community edition on the home's or group's server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
- Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing); other countries are priced per destination.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
UK: marketing to families
Under PECR, unsolicited marketing by electronic mail (including texts) needs consent or the soft opt-in, with a simple way to refuse. Replies to an enquiry are service; newsletters are marketing. General information, not legal advice.
Source: www.legislation.gov.ukUS: texts need the right consent
Promotional texts sent with automated technology need prior express written consent, so follow-ups to families are kept to the enquiry they made.
Source: www.law.cornell.eduEU and UK: health details in enquiries
Families often describe a relative's health; that is special category data under Article 9 GDPR and UK GDPR, so the CRM holds only what admissions needs.
Source: gdpr-info.euFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Care home CRM & admissions pipeline questions, answered.
A care home CRM tracks families and referrers from first enquiry to move-in: who called, who toured, who is waiting on funding or an assessment, and what happens next. It sits beside your care platform, which holds care records once someone moves in.
Senior living CRMs such as WelcomeHome and Aline are built around tours and move-ins; general CRMs such as HubSpot are flexible and well documented. We help you choose and can work with a CRM you already have.
Respond fast, book tours quickly, follow up kindly and know which sources lead to move-ins. The pipeline and report make that visible; the decision to admit stays with the manager.
No. Each sequence has a couple of messages at most, stops when the family replies or decides, and respects opt-outs.
Yes. Referrals from discharge teams or social workers get their own stage and an urgent task for the admissions lead, since they often need a quick answer.
Enquiries by source, time to first reply, tours booked, assessments, move-ins and average days from enquiry to move-in.
Free 20-minute call
Want this for your care home?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for care homes
All servicesRota gap filling & agency booking
When a caregiver calls in sick, the open shift is offered to suitable bank and pool staff in order, agency requests are prepared if nobody accepts, and the manager approves who fills it.
From $1,000 · About 4 weeks Details
Staff training matrix & compliance tracking
One live training matrix for employed and agency staff, with reminders before certificates and checks expire, recruitment documents tracked and an evidence pack ready for inspection.
From $1,000 · About 4 weeks Details
Family updates & visit booking
Family emails sorted and routine updates drafted for staff to approve, visits booked online with confirmations, and concerns routed straight to the manager.
From $1,000 · About 4 weeks Details