> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/control-panel-overview/communications-overview/setup-recurring.md).

# How to Set Up Recurring Messages

### Before you begin (Prerequisites)

* **Permissions**: You must be an **Administrator**, **Supervisor**, **Manager**, **Support**, or **Account Rep**. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md).
* **Recipients**: A group or segment must be defined for the audience.
* **For SMS**: Twilio must be connected. See: [How to Set Up Twilio](/products/integrations-overview/setup-twilio.md).

### Instructions

#### Recurring email

1. Build a **Marketing Newsletter** following [How to Build & Send an Email Newsletter](/products/control-panel-overview/communications-overview/build-send-email-newsletter.md).
2. While building, add **dynamic content** snippets so each send refreshes automatically:
   * **Recent Blog Posts** — auto-pulls latest blog entries each send.
   * **Upcoming Events** — auto-pulls the next N events from the calendar.
3. In the **SCHEDULE** section, click **SCHEDULE WHEN TO SEND**, select **Recurring Send**, and choose the frequency: **Daily**, **Weekly**, or **Monthly**.
4. Click **+ SELECT RECIPIENTS** to choose the audience group or segment.

> **Note**: Each recurring send auto-generates fresh content if you use dynamic content snippets. A weekly newsletter with event and blog snippets updates itself without manual editing.

> **Warning**: The newsletter must be in **Approved** status before the recurring schedule will fire. If it stays in Pending, no sends will occur.

#### Recurring SMS

1. Navigate to [**CONNECT > Manage SMS**](https://control.peoplevine.com/newsletters?message_type=sms).

> **Note (Pro Dash):** Navigate to **CONNECT > Group Messaging > View SMS Blasts**.

2. Click **COMPOSE SMS BLAST**.
3. Set **Delivery Medium** to **Text Message (SMS)** and **Type** to **Marketing Newsletter**.
4. Enter the **Campaign Name** and **Newsletter Message** (plain text — SMS does not support HTML or images).
5. Click **CONTINUE**.
6. Click **REVIEW & APPROVE FOR SENDING** to approve.
7. In the **SCHEDULE** section, click **SCHEDULE WHEN TO SEND**.
8. Select **Recurring Send** and choose the frequency.
9. Click **+ SELECT RECIPIENTS** to choose the audience.

### What Happens Next

* **On the member side**: Members receive the message on the configured schedule.
* **Tracking**: Monitor delivery, opens, and clicks from [**CONNECT > View E-mails Sent**](https://control.peoplevine.com/messaging/email/sent).

> **Note (Pro Dash):** Navigate to **CONNECT > Individual Messaging > E-mails Sent**.

* **Next step**: To automate messages based on member actions instead of a schedule, see: [How to Set Up Triggered Emails](/products/control-panel-overview/communications-overview/setup-triggered-emails.md).
* **Related**: To build multi-step automated sequences, see: [How to Create a Campaign](/products/control-panel-overview/communications-overview/create-campaign.md).

***

*Last updated: 2026-06-21*


---

# 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, and the optional `goal` query parameter:

```
GET https://help.peoplevine.com/products/control-panel-overview/communications-overview/setup-recurring.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.