Family communication and visit booking for care homes
Relatives want news, visits and answers, and their calls arrive during medication rounds and mealtimes. We build a workflow that sorts family messages, drafts routine updates from the day's notes for a senior to approve, books visits online with confirmations and sends concerns and complaints straight to the manager. A typical build costs $1,000 to $2,500 and takes about four weeks.
The problem
Why family calls pull caregivers away
Families are part of care, and keeping them informed builds trust. But a caregiver taking a call about how mum slept is not with residents, and messages left with whoever answers can get lost between shifts.
Sharing has rules. A resident's wishes, their capacity and who is their representative decide what each relative can be told, and a concern raised in a casual message may be a complaint or a safeguarding matter that needs the manager.
What we build
What our family communication automation includes
Family message sorting
Emails and web messages sorted into visit request, update request, practical question, concern or complaint.
Drafted routine updates
Short updates drafted from the care platform's notes for a senior to edit and approve before sending.
Visit booking
Online visit booking with confirmations, capacity rules per time slot and reminders.
Who may be told what
Each resident's contacts and sharing preferences checked before anything is drafted.
Concern routing
Concerns and complaints go straight to the manager with the message attached.
Monthly family newsletter
A home-wide newsletter, with no personal information, drafted for approval.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Message arrives
A family email or form is received and sorted.
-
02
Automated
Sharing checked
The resident's contacts and preferences decide what may be drafted.
-
03
Automated
Update drafted
A short update is drafted from the day's notes or a visit slot offered.
-
04
Office or senior review
Senior approves
A nurse or senior caregiver edits and sends each update.
-
05
Registered manager or nurse decides
Concerns
Concerns, complaints and anything about safeguarding go to the registered manager.
How it behaves
How family updates behave
What the family sees
- A prompt acknowledgement of every message
- Updates written and sent by a person they know
- Online visit booking with reminders
What staff see
- Drafts ready to approve
- Visit schedule for the day
- Concerns flagged to the manager
What the automation does
- Sorts messages and checks sharing rules
- Drafts updates and books visits
- Routes concerns and logs everything
Edge cases and fallbacks
- Relative is not a listed contact
- No resident information is shared; the manager is told.
- Message hints at abuse or neglect
- Sent to the manager at once under the safeguarding process.
- Visit slot is full
- The next slots are offered automatically.
- Care platform unavailable
- No drafts are produced; families get an acknowledgement and staff are alerted.
Architecture
Family updates and visit booking at a glance.
- Input
- Logic and services
- Data
- AI step
- Output
- People
How it flows
- 1 Family messages arrive by email or web form and are sorted.
- 2 The resident's contacts and sharing preferences are checked first.
- 3 Routine updates are drafted from the day's notes and visit slots are offered online.
- 4 A senior approves each update; concerns go straight to the manager.
Project planner
How the project runs, phase by phase.
Family updates & visit booking project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
How families contact the home, visit rules, sharing practice and the care platform.
-
02
Design
2 to 3 days
Message types, update wording, visit slots and concern routing.
-
03
Build
1 to 2 weeks
Sorting, sharing checks, drafts, visit booking and alerts.
-
04
Shadow run
About 1 week
Drafts are produced but not sent while seniors compare them with what they would write.
-
05
Launch
1 to 2 days
Go live for visit booking first, then updates.
-
06
Support
Ongoing
Wording changes and new message types.
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. If you already use a family app, we connect to it rather than duplicate it. Messaging and n8n are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- 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.
- 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.
- AI model usage: Billed by the provider per use; short drafting and sorting steps are usually a small monthly amount at care home volumes.
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.
US: sharing with family involved in care
HIPAA permits disclosures to family members involved in a resident's care that are directly relevant to that involvement, where the resident agrees or does not object, or on professional judgment. General information, not legal advice.
Source: www.law.cornell.eduUS: telling representatives about changes
Nursing homes must notify the resident's representative of events such as an accident with injury or a significant change; those calls stay with nurses, never automated.
Source: www.law.cornell.eduEU and UK: health data
Updates about a resident's wellbeing are health data under Article 9 GDPR and UK GDPR, so drafts use only what the update 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
Family updates & visit booking questions, answered.
They get updates a nurse or senior caregiver has read, edited and sent. The draft saves typing; the person decides what is said.
Each resident's contacts and sharing preferences are recorded and checked before anything is drafted. If it is unclear, the message goes to the manager.
Yes. They choose a slot, get a confirmation and a reminder, and the home sets capacity per time slot.
Those calls are made by a nurse or the manager, as the rules require. The workflow never sends news like that.
No. If you use one, we connect to it where the vendor allows and fill the gaps around it.
Time to reply to family messages, visits booked online, concerns routed to the manager and calls taken by caregivers during rounds.
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 servicesCare home CRM & admissions pipeline
Every family enquiry from calls, web forms, directories and hospital discharge teams lands in one care home CRM pipeline, from first call to tour, assessment and move-in, with follow-ups that never feel pushy.
From $1,000 · About 4 weeks Details
Rota 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