---
title: "Prepared Messages"
slug: "messages-prepared-messages"
updated: 2025-09-04T09:38:43Z
published: 2025-09-04T09:38:43Z
---

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

# Prepared Messages

## Introduction

A prepared message is a saved message assigned to a group. Mapp Engage gives every prepared message a message ID (MID). You can send a prepared message as a single message or as a group message. A single prepared message can be reused across multiple sendouts, which enables automated, multi-step programs in Whiteboard. The prepared message remains visible in the Prepared Message Overview window and can be edited at any time, even if it is used in a segment or whiteboard.

---

## Common Use Cases

- Reuse one prepared message for repeated or scheduled sendouts in Whiteboards.
- Create event-based or time-based workflows that send a prepared message.
- Build segments based on recipient behavior for a prepared message, for example, opens, clicks, and conversions. The segment covers all sendouts of that prepared message, past and future, single and group.
- Use prepared messages as templates for system messages.

---

## Working with Prepared Messages

Prepared messages act as reusable assets with a unique MID. Once created, they remain visible in the [Prepared Message Overview](/v1/docs/prepared-messages-overview-window) window and can be updated at any time. This flexibility ensures that even when a prepared message is part of a segment or whiteboard, you can still adjust its content without interrupting ongoing sendouts.

Prepared messages are often used within Whiteboard workflows. A whiteboard can reference one or more prepared messages in its setup, whether the job is event-based or time-based. Whenever you update a prepared message, the new content is automatically applied in future sendouts, keeping the workflow current without requiring additional configuration.

You can send a prepared message either as a single message or as a group message. It is important to understand the differences. See [Single vs. Group Sendouts of Prepared Messages](/v1/docs/single-vs-group-sendouts-of-prepared-messages)​.

### Example: Birthday Campaign

Bob, a marketing manager, creates an empty prepared message named `BirthdayEmail`. He sets up an automated birthday campaign in Whiteboard and links it to this prepared message. He also builds a segment that identifies contacts who click on the birthday email.

### Example: Content Updates on the Fly

Anne, responsible for email content, later opens the Prepared Message Overview window and updates `BirthdayEmail` by changing a coupon, refreshing the graphics, or testing a new subject line. The whiteboard continues running as planned, and future sendouts use the updated content automatically.

## Related

- [Save Draft as Prepared Message](/save-draft-as-prepared-message.md)
- [Single vs. Group Sendouts of Prepared Messages](/single-vs-group-sendouts-of-prepared-messages.md)
- [Create Templates for System Messages](/create-templates-for-system-messages.md)