> ## Documentation Index
> Fetch the complete documentation index at: https://docs.valaclaims.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Messages

> Review and send secure messages in a Client record.

## Overview

Use **Messages** in a Client record to review the secure conversation with the Client, reply, and share relevant attachments. Unread Client messages are highlighted elsewhere in Vala to help surface messages that need attention. Opening the Client's Messages conversation marks those unread Client messages as read.

<img src="https://mintcdn.com/vala/Kbb5xaypKnuoA7df/images/client-record/messages.png?fit=max&auto=format&n=Kbb5xaypKnuoA7df&q=85&s=ce8a6de24ca56c291b8a9dc6e4da6e0a" alt="The Messages tab showing a Client conversation and message composition controls." width="1440" height="900" data-path="images/client-record/messages.png" />

*The conversation view keeps Client messages and their context together.*

## Send a message

<Steps>
  <Step title="Open the conversation">Open the Client record and select <strong>Messages</strong>.</Step>
  <Step title="Review new messages">Read the conversation and confirm the Client context before replying.</Step>
  <Step title="Compose the message">Write a clear message for the Client.</Step>
  <Step title="Add attachments when needed">Attach existing Client Documents, upload a new attachment, or attach eligible reusable organization Documents.</Step>
  <Step title="Use a template when available">Select a message template from <strong>Templates > Messages</strong>. Customer-visible template variables are filled from the available Client and sender information.</Step>
  <Step title="Send and follow up">Review the message and attachments, then send. Choose an optional follow-up cadence when that control is available.</Step>
</Steps>

When Messages surfaces portal invitation context, staff can send or resend an invitation where their role allows it. Confirm the Client's email and the intended recipient before sending.

## Best practices

* Keep messages specific to the Client and the next action.
* Review selected documents and reusable attachments before sending.
* Use templates as a starting point, then verify the resulting message and variables.

## Related pages

<CardGroup cols={2}>
  <Card title="Templates > Messages" icon="message-square" href="/core-workflows/message-templates">Create and maintain reusable message templates.</Card>
  <Card title="Documents" icon="folder-open" href="/core-workflows/documents">Review Client documents before attaching them.</Card>
</CardGroup>
