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

# Communication

The **Communication Actions** allows your AI agent to send outbound messages to users or team members through supported channels.

These actions are commonly used for confirmations, reminders, alerts, follow-ups, escalations, and other automated notifications triggered during the flow.

Communication actions can be used after collecting required contact details such as email address or phone number, and they may run either synchronously or in the background depending on the selected configuration.

![Communication](https://mintcdn.com/monobot-0e0ffe36/yVZ9w6FeuKr7UZXp/images/settings/actions/communication/communication.png?fit=max\&auto=format\&n=yVZ9w6FeuKr7UZXp\&q=85\&s=01eee431c34abb62b988041bcebe2ec3)

## Supported Actions

This section includes:

* **Send Email**
* **Send SMS**

Both actions are designed for direct communication and can be used in booking flows, support flows, operational notifications, and post-interaction automations.

***

## Integration Requirements

Before using communication actions, ensure all required configurations are set up.

* **Email (SMTP)** requires a configured SMTP integration in the **Integrations** tab. See [Send Email (SMTP)](https://docs.monobot.ai/agent-settings/integrations.md)
* **SMS** requires a phone number assigned to the bot on **General** tab

Without proper configuration, the actions will not execute successfully.

***

## General Configuration

Each communication action includes general configuration fields before the action-specific parameters.

### Action Name

Defines the internal action identifier.

Examples:

* `smtp_send_email`
* `send_sms`

### Description

Defines the purpose of the action and how it should be used in the flow.

Examples:

* `Send an email via SMTP to a specified recipient (subject + body) to communicate with clients or partners.`
* `Send an SMS message to a specified phone number to notify or communicate with clients.`

### Async

If enabled, the action runs in the background and the bot continues the conversation without waiting for the result.

Use async mode when the delivery result is not needed immediately in the next step of the flow.

***

## Send Email

The **Send Email** action sends an email via SMTP to one or more recipients.

This action is useful for confirmations, booking summaries, follow-ups, internal notifications, escalation emails, and other automated communication scenarios.

To use Email actions, you must configure the integration (navigate to the **Integration** tab). See [Send Email (SMTP)](https://docs.monobot.ai/agent-settings/integrations.md)
for the details.

### Parameters

> **SMTP Auth Preset**
>
> **Type**: `string`\
> Preconfigured SMTP authentication preset used to send the email.
>
> This field defines which SMTP credentials and connection settings will be used for delivery.

> **Sender**
>
> **Type**: `string`\
> Email address of the sender.\
> *Example:* `sender@mail.com`
>
> This field defines the email address that appears as the sender.

> **Recipient**
>
> **Type**: `string`\
> Primary recipient email address.\
> *Example:* `recipient@mail.com`
>
> This field is required and defines the main destination for the email.

> **CC**
>
> **Type**: `string`\
> Comma-separated list of CC recipients.\
> *Example:* `cc1@mail.com, cc2@mail.com`
>
> Use this field when additional recipients should receive a visible copy of the email.

> **BCC**
>
> **Type**: `string`\
> Comma-separated list of BCC recipients.
>
> Use this field when additional recipients should receive a hidden copy of the email.

> **Subject**
>
> **Type**: `string`\
> Subject line of the email.
>
> This field is required and should clearly describe the purpose of the message.

> **Required Parameters**
>
> **Type**: `string`\
> Additional required parameters used by the action, if configured.
>
> This field can be used when the action expects extra structured values before execution.

> **Link for Attachment File**
>
> **Type**: `string`\
> URL to a file that will be attached to the email.
>
> Use this field when the action should include an external file as an attachment.

> **Output**
>
> **Type**: `string`\
> Custom success message returned after sending.\
> Default: `Email has been successfully sent.`
>
> This value can be used in the flow after the action completes successfully.

> **Message**
>
> **Type**: `string`\
> Email body content.
>
> This field contains the actual message sent to the recipient and may support rich text formatting depending on the editor configuration.

> **Only if everything was successful**
>
> **Type**: `boolean`\
> Runs the action only if all previous steps were completed successfully.
>
> Use this option when email delivery should depend on successful completion of earlier flow logic.

***

## Send SMS

The **Send SMS** action sends a text message to a specified phone number.

This action is useful for quick confirmations, reminders, short alerts, booking updates, status notifications, and other direct mobile communication scenarios.

### Parameters

> **To**
>
> **Type**: `string`\
> Recipient phone number.\
> *Example:* `+15551234567`
>
> This field is required and defines the destination number for the SMS message.

> **Message**
>
> **Type**: `string`\
> SMS message content.
>
> This field is required and contains the text that will be sent to the recipient.

> **Output**
>
> **Type**: `string`\
> Custom success message returned after sending.\
> Default: `SMS has been successfully sent.`
>
> This value can be used in the flow after successful message delivery.

> **Only if everything was successful**
>
> **Type**: `boolean`\
> Runs the action only if all previous steps were completed successfully.
>
> Use this option when SMS sending should depend on successful completion of earlier actions or validations.

***

## How Communication Actions Are Used

Communication actions are usually triggered after the flow has already collected the required delivery data.

Typical examples:

* send an email after creating a reservation
* send an SMS reminder before an appointment
* send a follow-up email after a support request
* send an alert to a manager or operator

These actions can be connected to booking flows, support flows, lead flows, or internal automation logic.

***

## Best Practices

* validate email addresses and phone numbers before sending
* ensure all required message content is prepared in advance
* use async mode only when immediate result handling is not needed
* keep SMS content short and clear
* use email for detailed communication and SMS for short notifications
* define output messages clearly when they are used in later flow steps

***

## Notes

* Email delivery requires a valid SMTP preset
* SMS delivery requires a valid phone number in the expected format
* Async mode allows the bot to continue the conversation without waiting
* Communication actions should be triggered only after all required data is available


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.