Secure Messaging

Secure messaging that keeps caregivers, agencies, and families in sync

A HIPAA-conscious messaging layer built into the same platform as scheduling, medications, and care plans — so conversations about a recipient’s care stay connected to the record, not scattered across text messages.

What’s included

One secure channel, not four text threads

Caregivers, agency staff, and families message each other inside the platform instead of over personal phone numbers and group texts, keeping care-related conversation off channels that were never built to handle it responsibly.

Shift summaries and care-plan context, in thread

Messages about a recipient sit alongside the shift notes and care plan information that give them context, so a family asking about today’s visit isn’t starting from zero — the relevant details are already close at hand.

Urgent alerts that don’t get lost

Time-sensitive messages are flagged as urgent so they stand out from routine updates, helping agencies and families respond quickly when something about a recipient’s care actually needs immediate attention.

Built on the platform’s security model

Messaging runs on the same architecture as the rest of Curalis: TLS 1.3 in transit, tenant data isolated with Postgres row-level security, and activity captured in an audit log — the same foundation, not a bolted-on chat tool.

Frequently asked questions

Is this a separate app from the rest of Curalis?

No. Messaging is part of the same platform as scheduling, medications, and care plans, so a conversation about a recipient can reference the shift or care-plan detail it’s about without switching tools.

How are urgent messages different from regular ones?

Urgent messages are flagged so they’re visually distinct and easier to spot, helping the right person notice and respond to a time-sensitive update about a recipient’s care faster than a routine message would get seen.

What keeps messaging data secure?

Messaging relies on the same protections as the rest of the platform: TLS 1.3 for data in transit, tenant isolation enforced with Postgres row-level security, audit logging of activity, and account protections like two-factor authentication and session timeouts.

Ready to simplify care coordination?

Start free trial