Live home intelligence · Australian pilot

One voice. One worker app. One live view across every supported home.

BellBots Home OS connects support workers, participants, each home and provider operations. Everyday work can be spoken naturally, completed safely and understood across the organisation.

Natural voicePermission scopedOne home to a fleet

Home 001

Morning shift

Bell online

2

on shift

Closed

doors

3

reminders

Hey Bell, Ronald had a gluten-free toastie and a can of Pepsi for lunch.
I’ve prepared Ronald’s lunch and drink entries. Please review them before I save anything.
Grounded voice captureReady to confirm

Shift Copilot · recommended next

Complete the open outing record

Andy · Ronald · Home 001 · verified shift

4 connected experiences

One shared Bell

Home-aware

Context follows the shift

Governed records

Review and provenance

Fleet-ready

Grow with control

One Bell · Four connected experiences

The system meets each person where they work.

Bell shares one intelligence layer while every experience stays inside its own permissions. Workers get immediate support, managers get fleet clarity, service partners see only their approved jobs, and each home remains the local authority for its devices.

Inside the home

Hey Bell is present when support is happening.

Workers speak naturally while Bell uses the active home, participant and checked-in worker to understand the request. Bell can answer grounded questions, record everyday support and control permitted home devices.

  • Natural speech
  • Home and participant context
  • Review before sensitive records

Worker

Hey Bell, Ronald just completed 20 minutes of art.

Bell

I’ve prepared an activity entry for Ronald: arts and crafts, 20 minutes. Would you like me to save it?

Permission-scoped · grounded · reviewable

One conversation · wherever work happens

Start with Hey Bell. Continue privately on the phone.

Bell carries the verified home, worker, participant and details already captured. A worker can move out of earshot and continue the same guided request without starting again.

No repeated explanation
Only the checked-in worker can resume
Sensitive text stays out of general language learning
Hey Bell · Home 001Verified shift

“Hey Bell, I need to report a maintenance issue. The bathroom light keeps flickering.”

Bell has the issue and room. It still needs the worker’s stated priority.

Same protected workflow
Bell Worker · privateReady to continue

Bathroom light maintenance request

Bell asks: “How urgent is this request?”

A shift with Bell

Less hunting. Less repeating. A clearer day.

Bell supports the flow of a real shift from check-in to handover, keeping everyday work connected without asking workers to learn a rigid command language.

01

Worker checks in

Verified identity, home and shift permissions become active.

02

Shift Copilot sets the order

Bell ranks recorded attention items, explains why and gives the safest next step.

03

Support is captured naturally

Meals, drinks, activities, outings and observations can be spoken or typed.

04

Bell fills the gaps

Guided questions collect only the missing details for maintenance, shopping or incident assistance.

05

Private work continues on the phone

A request started with Hey Bell can continue in Bell Worker without repeating captured details.

06

The right reminders reach the shift

The home speaks the reminder while opted-in phones chime only for workers still checked in there.

07

Everyday needs stay organised

Participant and household lists keep separate history, context and purchasing status.

08

The shift closes clearly

Outstanding items and verified records support a stronger, reviewable handover.

Shift Copilot

Know what needs attention before searching for it.

Bell orders current work from verified Home OS records. It explains why an item appears and gives the next safe operational step without making clinical or reportability decisions.

3

need attention

5

shift events

1

recorded out

Illustrative shift information

Recommended next

Complete the incident-assist account

Why this is here

The private account is missing the immediate actions recorded by the worker.

Safe next step

Continue privately, add the missing fact and review the captured account before it enters the governed workflow.

Ronald is recorded out

Panthers · open outing since 12:10 pm

Bins reminder due

Home and checked-in phone reminder

For owners and operators

Ask the fleet a question. See where to act.

Ask Bell helps authorised leaders move from a natural question to the homes, records and controls behind the answer. It can carry the subject and time across follow-up questions while keeping each result grounded.

Interactive example · synthetic information only

Ask Bell

Fleet intelligence

Live records

You asked

Which homes have participants out and lights still on?

2 homes need review

home001 · kitchen and hallway | home004 · lounge

Natural follow-up

“Now show only the homes with no worker currently checked in.”

Authorised homes
Source records
Confirmed actions

Everything works from the same context

Built around the work a supported home actually does.

Every capability shares the verified home, participant, worker and permission context. Information moves through the day instead of becoming another isolated record.

People supported

Participant-specific support stays connected across the day.

  • Meals, drinks and hydration
  • Exercise, activities and daily observations
  • Outings, current location and return
  • Participant and household shopping lists

Workers and shifts

The signed-in worker and active home shape every permitted action.

  • Workforce and home assignments
  • Check-in, check-out and worked hours
  • Shift Copilot and verified timeline
  • Handovers and private unfinished work

The connected home

The home hub remains the local authority for devices and sensors.

  • Lights, colours, television and timers
  • Door, motion and temperature questions
  • Fresh telemetry and hub health
  • Home-scoped remote controls

Records and follow-through

Bell asks for missing facts before a governed record moves forward.

  • Guided incident assistance
  • Editable maintenance requests
  • Medication-assistance history questions
  • Reminders, acknowledgements and audit trail

Provider intelligence

Authorised leaders can ask across one home or the whole fleet.

  • Natural fleet questions and follow-ups
  • Attendance, incidents and operational trends
  • Participant presence and home attention
  • Confirmed device actions by home

Service Network

Approved external providers can complete work without entering care records.

  • Category and home eligibility
  • Offer, acceptance and arrival status
  • Before-and-after evidence
  • Provider completion review

Bell Service Network

A maintenance request can move without getting lost.

Bell connects the worker’s request, approved service companies, job progress and completion evidence. The provider keeps oversight and handles payment separately in its existing system.

Request

Captured

Provider

Accepted

Evidence

Attached

Review

Controlled

01

Worker reports the need

Hey Bell or Bell Worker gathers the issue, exact area, stated priority and immediate safety details.

02

Bell routes the request

Eligible approved companies receive the job according to the provider’s category, home and priority rules.

03

A provider accepts

The worker and provider can see who accepted, the current status and the recorded arrival estimate.

04

Evidence follows the work

The job requires before-and-after evidence through provider-approved private storage, with time-stamped events.

05

The provider reviews completion

Evidence and job history stay in Bell while the provider handles payment through its own system.

Service partners stay outside participant care records

Their access is limited to approved jobs, properties, status updates and service evidence.

Permission scoped

Intelligence with boundaries

AI understands.
Policy decides.

Bell can interpret natural language, but permissions, required fields, confirmation and deterministic handlers remain outside the language model.

Soft OK safety stays underneath every experience

The same boundaries follow Hey Bell, Bell Worker, Ask Bell and Bell Service Partner.

What that means in practice

  • A worker identity is attached to governed actions
  • Role, provider, home and active-shift permissions are checked again by the backend
  • Sensitive actions require the missing facts and worker confirmation
  • Bell does not invent clinical claims or make clinical decisions
  • Cameras remain off by default
  • Incident data is prepared for review and future Auditly handoff, not sent directly to the Commission

Incident information path

Bell captures
Provider reviews
Auditly handles authorised submission after connection

Bell does not decide reportability and does not submit directly to the NDIS Commission.

Privacy, support and clear processing information are publicly available.

Grow without losing the home

Start with one. Repeat with confidence.

Each property receives its own Bell hub, verified devices and home profile. The organisation connects those homes into one governed fleet while local operation and home permissions remain clear.

1

pilot home

10

connected homes

1,000+

future-ready

Bell fleet
Home 001
Home 004
Home 018
New home

Questions

Understand Bell before it enters a home.

No. Bell reduces friction around information, home operations and record capture. People remain responsible for care, judgement, review and action.

See what one supported home feels like with Bell.

Walk through Hey Bell, Bell Worker, Ask Bell and Bell Service Partner as one connected operating system built around a real shift.

Real home walkthroughWorker and provider viewsQuestions welcome

Request a Bell walkthrough

Tell us enough to prepare the right demonstration.

This opens a prepared email to info@bellbots.com. Your details are not stored on this page.