> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-messages-actions.md).

# Agentic Workflow Messages Actions

{% hint style="success" %}
**Audience:** Administrators, Developers, Solution Architects

**Purpose:** Reference for the Send Email and Send Text actions available in <code class="expression">space.vars.contact</code> <code class="expression">space.vars.automations</code>, covering configuration options, behavioral notes, and error handling.
{% endhint %}

## Overview

Messages actions send communications to the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> in context. These actions are only available when the <code class="expression">space.vars.automation</code> is built on a <code class="expression">space.vars.contacts</code> <code class="expression">space.vars.object</code>; they do not appear in <code class="expression">space.vars.automations</code> built on other <code class="expression">space.vars.object</code> types such as <code class="expression">space.vars.objects</code> or <code class="expression">space.vars.workflow</code> stages.

Two actions are available:&#x20;

* **Send Email:** sends a templated or newly composed email to the <code class="expression">space.vars.contact</code>.&#x20;
* **Send Text:** sends a plain-text SMS message to the <code class="expression">space.vars.contact</code> using your configured text messaging provider.&#x20;

Both actions support merge fields for personalization and share the same error handling model as other action steps.

{% hint style="info" %}
**Note:** For error handling, see [Agentic Workflow Error Handling](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-error-handling.md).
{% endhint %}

***

## Send Email

The Send Email action sends an email to the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> currently in context.

<div data-with-frame="true"><figure><img src="/files/UWVQTrYdu3QrUIdx52qB" alt="" width="237"><figcaption></figcaption></figure></div>

**Additional Description:** An optional freeform text field for internal notes about the step. This value is not included in the email.

**CC Team Members:** Use the **CC Team Members** dropdown to copy one or more team members on the outgoing email. The following options are available:

* **None:** No team members are copied. This is the default.
* **Last Active Team Member (Any Role):** Copies the most recently active team member on the <code class="expression">space.vars.entity</code>, regardless of role.
* **Last Active Team Member (Specific Role):** Copies the most recently active team member on the <code class="expression">space.vars.entity</code> who holds a specified role.
* **Specific Team Members:** Copies one or more named team members selected at design time.
* **Custom Team Selector Field:** Copies the team member resolved by a team selector field on the context <code class="expression">space.vars.entity</code>.

**Choose Email To Send:** Select or create the email to send using one of two options:

* **CHOOSE EMAIL FROM LIBRARY:** Opens the **Choose Email Template** dialog, where you can browse and select from saved Templates, Broadcasts, or <code class="expression">space.vars.automations</code> emails.
* **CREATE NEW EMAIL:** Opens the email builder to compose a new email directly.
* Based on your email account type, a daily quota applies to emails sent via the selected integrated inbox

***

## Send Text

The Send Text action sends a text message to the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> currently in context.

<div data-with-frame="true"><figure><img src="/files/1znfX3Ii3MjwQDl4of9b" alt="" width="236"><figcaption></figcaption></figure></div>

**Additional Description:** An optional freeform text field for internal notes about the step. This value is not included in the message.

**Text Message Body:** Compose the message content in the **Text Message Body** field. Use **+ INSERT MERGE FIELD** to insert dynamic values from fields on the context <code class="expression">space.vars.entity</code>. Available merge fields are organized by category; for example, the **Contact Info** category includes fields such as Link to <code class="expression">space.vars.entity</code>, First Name, Last Name, Email, and Date Created.

{% hint style="warning" %}
**Note:** Sending text messages requires an active Twilio integration. See [Twilio SMS](/docs/integrations-and-plugins/integrations/twilio-sms.md) for instructions on connecting your account and provisioning a sending number.
{% endhint %}

The body supports up to 10 message segments of 153 characters each, for a maximum of 1,530 total characters. The character counter below the field displays remaining characters in the current segment and total characters used.

***

## Key Use Cases

Messages actions are applicable across any <code class="expression">space.vars.workflow</code> that requires direct communication with <code class="expression">space.vars.contacts</code> at a defined point in an automated process. The following examples illustrate common patterns in three industries where timely, automated outreach is a core operational requirement.

### Industry Examples

{% tabs %}
{% tab title="Insurance" %}
Insurance operations depend on prompt, accurate communication with policyholders and claimants at key points in the policy and claims lifecycle.

Examples include:

* Using Send Email to deliver a policy renewal notice to the <code class="expression">space.vars.contact</code> when an <code class="expression">space.vars.automation</code> detects an upcoming expiration date, with merge fields populated from the policy record
* Using Send Text to send an immediate SMS confirmation to a claimant when a new claim record is created and the <code class="expression">space.vars.automation</code> reaches the notification step
* Using Send Email to notify a <code class="expression">space.vars.contact</code> of a coverage change or endorsement, attaching a templated summary email composed in the email builder
* Using Send Text to follow up with a <code class="expression">space.vars.contact</code> who has not responded to a previous outreach, using a short merge-field-personalized message within the 1,530-character limit

How Messages actions help:

* Deliver policy and claims communications automatically at the right moment in the workflow, without requiring manual outreach from team members
* Personalize messages at scale using merge fields drawn from the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code>
* Maintain a consistent communication cadence across high-volume <code class="expression">space.vars.contact</code> populations such as renewal books or open claims queues
  {% endtab %}

{% tab title="Healthcare" %}
Healthcare workflows require reliable, timely communication with patients and <code class="expression">space.vars.contacts</code> at critical points in care coordination and administrative processes.

Examples include:

* Using Send Email to send an appointment confirmation or preparation instructions to a patient <code class="expression">space.vars.contact</code> when a scheduling <code class="expression">space.vars.automation</code> reaches the confirmation step
* Using Send Text to deliver a same-day appointment reminder to a patient <code class="expression">space.vars.contact</code>, keeping the message within a single 153-character segment for clarity
* Using Send Email to notify a <code class="expression">space.vars.contact</code> of a referral or care plan update, using a templated email selected from the library
* Using Send Text to follow up with a <code class="expression">space.vars.contact</code> after a care event, using merge fields to personalize the message with the <code class="expression">space.vars.contact</code>'s name and relevant details

How Messages actions help:

* Reduce no-show rates and improve patient engagement by delivering timely reminders and confirmations automatically
* Reach <code class="expression">space.vars.contacts</code> on their preferred channel — email for detailed communications, text for brief time-sensitive messages
* Keep outreach consistent and compliant by using pre-approved email templates selected from the library rather than ad hoc messages
  {% endtab %}

{% tab title="Financial Services" %}
Financial services <code class="expression">space.vars.workflows</code> require precise, well-timed communication with clients and prospects at key stages of onboarding, servicing, and renewal processes.

Examples include:

* Using Send Email to deliver an onboarding welcome message to a new client <code class="expression">space.vars.contact</code> when an <code class="expression">space.vars.automation</code> moves the associated <code class="expression">space.vars.entity</code> to an active status
* Using Send Text to notify a client <code class="expression">space.vars.contact</code> of a time-sensitive action required on their account, using a concise merge-field-personalized message
* Using Send Email to send a periodic statement or document notification to a <code class="expression">space.vars.contact</code>, referencing a templated email built in the email builder
* Using Send Text to follow up with a prospect who has not engaged after an initial outreach, keeping the message brief and including a merge field for the <code class="expression">space.vars.contact</code>'s first name

How Messages actions help:

* Automate high-touch client communications at key lifecycle moments without requiring advisor or operations team intervention
* Ensure consistent messaging across large client populations by using library templates with controlled content
* Reach clients quickly on mobile when time-sensitive action is required, without waiting for email open rates
  {% endtab %}
  {% endtabs %}

***

## What's Next?

Continue to [Agentic Workflow Code Steps](/docs/concepts/agentic-workflows/automation-code-steps.md) to learn how the execution engine processes action steps at runtime, including the asynchronous queue model, execution lifecycle, step isolation, and ordering guarantees.

<details>

<summary>Related Topics</summary>

* [Agentic Workflow Control Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-control-actions.md)
* [Agentic Workflow Field Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-field-actions.md)
* [Agentic Workflow Related Object Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-related-object-actions.md)
* [Agentic Workflow Team Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-team-actions.md)
* [Agentic Workflow Integration Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-integration-actions.md)

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.kizen.com/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-messages-actions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
