Staff-Initiated Threads
The organization opens the conversation and controls whether reply is allowed.
MESSAGING
Secure conversations that stay with the record.
SecureCare Messaging gives staff a governed channel for sensitive communication with customers and volunteers. Staff initiate the thread, control external access, and keep every message and attachment tied to the person’s record.
Record-Bound History
Threads live on the customer or volunteer record rather than in a separate inbox silo.
External Access Without an Account
Recipients can use a time-limited browser link when a Patron account is not appropriate.
Identity Verification
Sensitive threads can require supported identity checks before access is granted.
Document-Aware Attachments
Attach local files, organizational documents, or existing customer documents without duplicating storage unnecessarily.
HOW IT WORKS
Open the Thread to Retain the Record.
A guarantor, parent, or one-time volunteer can receive a secure browser link instead of being forced through account creation. Staff control the link duration and can require date-of-birth, phone, both, or neither for identity verification.
Open the Thread
Staff choose the recipient, subject, reply behavior, and access rules.
Choose Access
Use signed-in access or a temporary external link with an optional identity check.
Share the Conversation
Messages and attachments remain encrypted and tied to the record.
See Delivery & Reads
SecureCare shows sent/read state instead of assuming the recipient opened it.
Retain the Record
Attachments become Document Storage records and the thread remains part of the audit context.
A CLOSER LOOK
External access without creating another account.
A guarantor, parent, or one-time volunteer can receive a secure browser link instead of being forced through account creation. Staff control the link duration and can require date-of-birth, phone, both, or neither for identity verification.
Customers and volunteers cannot initiate arbitrary new threads; staff govern the outreach channel.
External access can be revoked before the configured expiration.
Failed identity checks are rate-limited and recorded in the authentication audit log.
Message bodies and attachments use the platform’s encrypted storage model.
Read indicators show whether the recipient actually opened the message.
Attachments sent or received become standard Document Storage records on the relevant record.
KEY CAPABILITIES
Messaging built around the real workflow.
Customer Threads
Keep secure customer communication on the customer record.
Volunteer Threads
Keep coordinator communication on the volunteer record.
Reply Control
Decide whether the external recipient may reply.
Temporary Links
Send secure browser access to recipients without Patron accounts.
Identity Checks
Require supported customer identity validation for sensitive access.
Attachment Sources
Attach local, organizational, or existing record documents.
Read Status
See sent and read state on the conversation.
Attachment Controls
Apply the documented file-size and file-type restrictions.
Document Storage Integration
Turn message attachments into retained record documents.
Audit Context
Retain access, reply, link, and authentication history with the thread.
CONNECTED ACROSS SECURECARE
Part of one connected platform.
Keep sensitive outreach governed, encrypted, and in the same record as the work it supports.
PEOPLE. PURPOSE. POSSIBILITIES.
Keep sensitive outreach governed, encrypted, and in the same record as the work it supports.
