For home care agencies

You find out a client is unhappy on the day they cancel.

VoiceRounds calls every client once a day, hears how they actually are, confirms the visit happened from the only person who really knows, and puts anything that needs a person into a named coordinator's hands.

Runs alongside your scheduling systemBuilt in Ontario, data stays in CanadaNo new app for your PSWs

Visits · Weston branch

Today, 9:42 AM

2 clients say nobody came.
29 confirmed by the client3 could not be confirmed2 say nobody came
Doris K.Nobody cameSays nobody came yesterday afternoon.
Alan P.DisagreementVisit marked complete. He says no one arrived.
Mei-Ling T.Cut short“She was in and out in ten minutes.”
Harold B.Not confirmedNot sure. Not the same as nobody coming.
Estelle R.ConfirmedConfirmed. Slept well, ate breakfast.

Illustrative. These are not real clients. No worker names anywhere on this board, by design.

Iris, the daily check-in call

Meet Iris

She asks the one person your schedule never asks.

Your roster tells you a visit was booked and your timesheet tells you it was billed. Neither can tell you whether anybody actually came, or stayed. Iris rings every client the next morning, unhurried and in their own language, and asks, which is how you hear about the ten-minute visit before the family does.

“Good morning Margaret, it’s Iris calling from Bayview Home Care. I’m an automated call, not a real person. I just wanted to see how you’re doing today.”

Her first sentence, on every call. Her name, then your agency, then what she is, before she asks anything. Bayview Home Care is an example; she names yours.

Margin, then safety

What a daily call pays for

The first two are pure arithmetic and happen every week in every branch. The fourth is the one that matters most and sells least, so it is last.

Churn you can see coming

A client who quietly did not get on with the new PSW cancels four weeks later, and you hear about it from the cancellation. A daily call hears it in week one, while it is still a scheduling problem rather than a lost client.

Trips you do not waste

A morning call that catches “I’m at my daughter’s today” saves a forty minute drive and an hour nobody can bill. Small each time, and it happens every week in every branch.

Visits confirmed by the person who received them

Your visit verification proves a phone was at the door. It cannot tell you the client was helped. She can, and she is the only one who can.

The hours nobody sees

Three hours of visits a week. One hundred and sixty five hours alone. You are accountable for all of it and you can currently see none of it.

This is what a cancellation sounds like four weeks out

Illustrative. These are not real clients.
Week 1

“The new girl is very nice.”

Week 2

“She’s in a bit of a rush, but it’s fine.”

Week 3

“I don’t like to make a fuss.”

Week 4

“I’ve been thinking about whether I still need this.”

Nothing here needed a clinician. It needed somebody in the office to change who was on that run, in week two, while it was still a scheduling problem.

What your visit verification cannot tell you

EVV confirms a worker was at the address. It cannot confirm the client was helped, that anybody stayed, or that the visit was any good.

This is not a way to check up on your PSWs, and it is built so it cannot become one. There is no per-worker score anywhere in the product, and there is not going to be one.

Asked only when a visit was actually scheduled

No visit on the books, no question. Asking a client whether somebody came when nobody was due makes the software look like it is guessing.

“I’m not sure” is recorded as not sure

A client who cannot remember is not evidence that nobody came. That distinction is written into the engine, because a lot of your clients have memory problems and none of them should cost somebody their job.

Findings go to a coordinator, not to a scorecard

A missed or poor visit lands on the office as a task for today. It never lands on a worker’s record, and your team never has to be told it is being watched, because it is not.

When two systems disagree, a person decides

If your records say the visit happened and the client says it did not, that is surfaced as a disagreement and left for somebody to look at. Software should not quietly pick a winner about whether a person received care.

Called this morning at 9:15Reached
Good morning, it’s Iris calling from Weston Home Care. I’m an automated call, not a real person. Is now a good time?
Yes, I’m just up.
How did you sleep?
Not too badly. My knee’s been grumbling.
Did someone come to see you yesterday?
No, nobody came yesterday.

What it heard

Knee pain mentioned. Yesterday's visit not confirmed by the client.

Who was told

Both passed to the Weston coordinator as tasks for this morning.

Illustrative. These are not real clients.

The question nobody asks until 3am

What happens when something goes wrong

Software that watches over people has to be judged on its worst day. Every claim below is a mechanism that exists.

Escalation runs on our servers

An urgent alert is escalated on a schedule by our infrastructure, not by a screen somebody left open. Nobody has to be logged in.

It climbs to your on-call

Unacknowledged alerts pass to the next person and finally to the named contacts on your own escalation ladder, by text, until somebody answers.

A watchdog checks the loop ran

If the calls or the escalations stop, we are paged. You should not be the monitoring system for the thing monitoring for you.

None of this replaces your staff, your phones, or 911. It means that when the software has a bad night, the failure is loud and lands on us.

Every rule that can ring a phone is written down

In plain English, dated, and readable inside the product rather than buried in a contract.

13 rules, 4 of which ring a phone

The rest raise something on a board without waking anybody, because a system that pages for everything is a system nobody reads.

Versioned, currently 2026.08.23.1

Every concern carries the version in force when it was raised. Changing a rule without changing the version fails our build.

Her words kept 90 days

The record is permanent. The verbatim transcript is not, because an offhand sentence should not follow somebody for the rest of their life.

It runs alongside what you already have

VoiceRounds does not schedule, route, bill, or replace your point-of-care app. It is the one thing none of those do, which is telephone the client. Import your client list by file to start; a live sync with your scheduling system is roadmap, not shipped, and we would rather tell you that now than during the pilot.

See it run on one of your clients.

Twenty minutes. We ring a line you nominate, live, and you watch the board react to what was actually said.

Book your demo

Before you buy

When you should not buy this

Some agencies will get nothing from this, and we would rather say so now than take a month of your time finding out.

You have fewer than about thirty clients

Below that you can ring them yourself, and you probably should. The value here starts when you can no longer remember which client sounded unhappy three weeks ago.

You want to know which worker is underperforming

Findings are grouped by client, never by worker, and we will not build the other view. If the reason you are buying is to build a case about somebody, this will frustrate you on purpose.

You need it to prove visits happened for billing

It cannot. Your schedule says a visit was booked and your visit verification says a phone was at the door. Iris asks the client how it went. That is a different question and it is not evidence for an invoice.

Your clients are mostly non-verbal or in crisis

A daily conversation needs somebody able to have one. For high-acuity caseloads the calls reach too few people to justify the cost.