Carer-Participant Contact Without Personal Devices, and How to Keep It Audit-Ready

The short answer

Support workers text clients from their personal phones because it is the fastest option in the moment, not because anyone decided it was acceptable. The fix is not a policy telling carers to stop -- it is giving them a channel that is just as fast and doesn't require handing over a number. Teiro does this by masking both sides of the conversation behind one platform number and logging every message to the client's record automatically, so the audit trail exists whether or not anyone remembers to create it.

The rest of this piece is why that gap exists, what it actually costs a care organisation, and how the fix works in practice.

Why this happens: the phone number was always going to end up somewhere

A support worker is fifteen minutes from a client's house and running ten minutes late. The office is the "correct" channel, but calling means waiting on hold, explaining the situation, and hoping someone relays it in time. Texting the client directly, or the client's daughter, takes eight seconds. Once that number is in a support worker's phone, it stays there -- for this visit, and every visit after it.

Multiply that by a roster of twenty or thirty support workers, each building up their own private list of client and family numbers over months or years, and a fact becomes hard to avoid: a meaningful share of your organisation's client-facing communication is happening on channels the organisation cannot see, cannot search, and does not control.

This is not a story about careless staff. It's what happens when the fastest available option and the organisation's actual policy point in different directions. Policy rarely wins that contest.

What it actually costs

No record of what was said. If a support worker tells a client's family "we've moved Tuesday's visit to 2pm" over text, and nobody wrote it down anywhere else, that conversation doesn't exist as far as your organisation's records are concerned. If it's later disputed, there's nothing to point to.

A number that doesn't come back. When a support worker leaves your organisation, they leave with every client and family number still sitting in their phone. Nothing in that departure process removes it. Your organisation has no way to confirm client contact details aren't still being used, or simply forgotten about, on a phone you have no relationship with anymore.

Nothing to hand over at handover. A coordinator who has been managing a client relationship for a year holds a lot of context that never made it into any system -- what the family gets anxious about, what's been tried before, what was promised. When that coordinator goes on leave or moves roles, their replacement starts from close to zero on anything that only ever happened by text or personal call.

A weak answer when someone asks for evidence. If a family member, an auditor, or a regulator asks how a specific change was communicated to a participant, "we believe someone texted them, but we'd need to check whose phone" is not a strong position for a provider to be in.

Why "just tell carers not to do it" doesn't work

Because it removes the fast option without replacing it with anything. A policy that says "always call the office, never text a client directly" is asking a support worker running late to choose between following the rule and actually getting the message across. In practice, the rule loses, quietly, because nobody's watching in the moment it matters.

The only policy that reliably works is one that makes the compliant option the fast option. That's a product problem as much as a policy one.

How masked messaging closes the gap

Teiro's approach keeps the experience close to what a support worker already does -- send a text -- while changing what happens underneath it.

One platform number, both sides masked. A client texts a single Teiro number and gets replies from it. A support worker messages from inside the Teiro app during their visit. Neither one ever sees the other's real mobile number. There's no number for a support worker to save, because their own number was never part of the exchange in the first place.

Two ways in, one record. A coordinator can start a conversation directly from the client's record -- picking the client or a nominated family member as the recipient before typing a word. A support worker messages from inside their visit, scoped to that client and that shift. Either way, the message lands on the same client timeline automatically.

Scoped to the visit, not an open line. The channel exists for day-of logistics -- running late, door codes, access -- and it closes when the assignment ends. It's deliberately not an always-on chat between one carer and one client; schedule changes, clinical questions, and anything more serious stay coordinator-mediated.

A masked-by-default number even in the record. Even the client's own phone number, sitting on their own record, is masked by default for every viewer -- staff included. Revealing it takes a deliberate action, comes with a warning, and creates its own entry in the audit log. It's a small piece of friction that nudges routine contact back toward the logged channel instead of a number getting copied into somewhere else.

Somewhere for a message to go outside the window. If a client texts in outside an active or upcoming visit, they get an automatic reply pointing them to the organisation's own on-call number, rather than the message sitting unread on an off-shift worker's phone. Teiro doesn't route to emergency services -- what a client should do in a genuine emergency stays the organisation's own protocol, set separately.

What this looks like for a family member instead of the client

A large share of aged care and disability clients can't use a phone themselves, or shouldn't be the one relied on to relay something important. Rather than treating "message the client" as the only option, a coordinator starting a conversation chooses the recipient first -- the client, or a recorded family member or representative -- so the conversation is with the right person from the first message, and it still sits on the client's own record either way.

Setting it up

There's nothing to buy or configure per organisation -- messaging runs on one shared platform number, and the masking and logging are on by default. The practical steps are getting your team onto the mobile app, making sure client (and family) phone numbers are on file, and sending a first message from a client record to see the full flow. The step-by-step version of this is in Setting Up Client Messaging in Teiro.

For the full feature walkthrough, see Message Clients Without Personal Phones.

Frequently asked questions

How do I stop support workers texting clients from their personal phones?

Give them a channel that's at least as fast. A support worker messaging from inside their visit in the Teiro app takes about the same effort as texting directly, but the client's number is never exposed to them and the message is logged automatically. Removing the fast option without replacing it (a "please don't" policy with no alternative) rarely holds up under real time pressure.

What happens to client contact details when a support worker leaves?

Nothing needs to happen, because nothing was ever exposed. A support worker's own mobile number is never part of a masked conversation, so there's no client number sitting in their personal phone to worry about when they leave.

Does masked messaging mean our coordinators can't see a client's phone number either?

No. A client's phone number is still their own contact detail, visible to coordinators with access to the record. It is masked by default in the interface and revealing it is logged, which is a different thing from being hidden from the organisation -- the masking that matters for carer-client contact is between the carer and the client, not between the organisation and its own records.

Is this only relevant to NDIS providers, or does it apply to aged care too?

It applies wherever a support worker or carer is in direct contact with a client or their family outside of scheduled office hours -- disability support, aged care, and community health all share the same underlying pattern of a fast personal-phone workaround filling a gap that a proper channel should close. The specific record-keeping expectations a provider needs to meet vary by program and should be confirmed against your own regulatory obligations; this guide describes the communication-channel problem and the product fix, not a compliance certification.

Can a client's family member reply on their behalf?

Yes. When a coordinator starts a conversation from the client record, they choose whether it's going to the client directly or to a recorded family member or representative, before the message is written. The conversation stays attached to the client's own record regardless of which contact is actually messaging.

Does this replace phone calls entirely?

No, and it isn't meant to. The channel is scoped to day-of logistics. Anything involving a schedule change, a clinical question, or an urgent or complex matter is still meant to go through a coordinator directly, by phone or however your organisation already handles it.

Want to see it running with your own client data? Book a demo or start free with up to five active users.