Communications and family
Bring operational messages, caregiver conversations, client communication, and approved family updates into a clear, accountable workflow.
What changes
Home-care teams do not need another disconnected inbox. They need to know which client, visit, schedule change, document, or exception a message is about—and what should happen next.
Connected capabilities
Each part of the workflow keeps its context, boundaries, and accountable owner.
Send schedule and open-visit communication through supported channels.
Ethiya Intelligence can help prepare a plain-language, time-bounded update from authorized source material while preserving the original and requiring review before sharing.
Authorized family members should be able to see the information the agency has chosen to share—such as schedules, visit completion, approved updates, and relevant communication—without receiving unrestricted access to internal notes or staff conversations.
Record the recipient, channel, consent basis, content version, sender or approving user, delivery outcome, response, and related workflow. If AI helped draft or transform the message, keep that visible to authorized reviewers.
Consent-aware communication
A useful update says what happened, what changed, and whether the agency is following up. It should not invent clinical meaning, expose unrelated information, or replace a direct conversation when the situation is sensitive.
Questions to ask
Two-way messaging should be described only for supported participants, numbers, message types, consent states, and delivery behavior in the release.
Ethiya can be designed to prepare a family-ready draft, but recipient authorization and human review should control external sharing. Automatic delivery requires an explicitly approved, bounded policy.
Translation is a roadmap capability unless verified. Any implementation should retain the original, label the translation, support review, and avoid representing it as a certified interpretation service.
Recorded or transcribed calls are not a general platform promise. Any supported workflow must disclose automation, obtain appropriate consent, provide a non-recording path where required, and apply retention controls.
See it in context
Bring one current workflow—open-visit outreach, a family update, a missed-visit follow-up, or a caregiver response—and we will show how Ethiya keeps it connected.
Request a communication demo↗