---
title: "Read Mode Configuration"
slug: "read-mode-configure-sent-message-format"
updated: 2025-09-01T12:04:16Z
published: 2025-09-01T12:04:16Z
---

> ## 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.

# Read Mode Configuration

## Overview

Read Mode in Mapp Engage determines which message format is sent to each recipient. If multiple formats exist for a message, Read Mode settings decide which version is delivered so the content displays correctly for every recipient.

---

## Key Characteristics

- **Available formats**
  - **Email (HTML):** Rich, styled email with images, fonts, and colors.
  - **Email (Text):** Plain-text email that displays reliably when images or HTML are restricted.
  - **Email (Multipart):** System-built when both HTML and Text exist, containing two or more formats for optimal inbox rendering. Mapp Engage sends multipart whenever possible. This ensures correct display without requiring complex layouts.
  - **SMS:** Available only if SMS sendout is enabled in your system.
  - **Online:** Formerly used when recipients read messages in Mapp Engage. Now it is primarily used to temporarily suspend delivery.
- **Where formats come from**
  - Formats can be created directly in the UI.
  - **Online** and **Email (Multipart)** are generated automatically from available formats.
- **Scope of settings**
  - **Group level:** You can set a preference for Email, Mobile Push, or SMS. There are no prohibitions at the group level and no distinction between HTML, Text, or Multipart email. Group preferences apply only when recipient settings are missing or unclear.
  - **Recipient level:** You can **allow**, **deny**, **prefer**, set **none** (deliver online only), or set **any** (accept all formats). Online can only be controlled at the recipient level. Preferences can be imported, for example, via XML or CSV.
- **System goal**
  - Mapp Engage prioritizes sendout. Unless a format is explicitly denied, the system attempts to send a message in an allowed format.

---

## Configuration and Behavior

### Recipient Read Mode options

- **Allow:** Format is permitted.
- **Deny:** Format is blocked for the recipient.
- **Prefer:** Format is chosen when multiple formats are available.
- **None:** The message is provided online only, and there is no sendout. This option is primarily used to interrupt delivery.
- **Any:** All formats are permitted.

### Group preference

Set the preferred channel in group settings. This sets a desired format but never blocks others. It applies only if recipient settings are absent or ambiguous. There is no separation between HTML, Text, and Multipart at the group level.

### Format decision sequence when preferences are ambiguous

If neither group nor recipient settings yield a clear choice, Mapp Engage selects the format using this internal order:

1. Email (Multipart)
2. Email (HTML),
3. Email (Text),
4. SMS

The formats available in the prepared message still govern what can be sent.

### How message format and Read Mode interact

| Recipient Setting | Group Setting | Resulting Behavior |
| --- | --- | --- |
| Recipient prefers **SMS** | Group prefers **Email** | System sends **SMS** (recipient preference overrides). |
| No specific recipient preference | Group prefers **Email** | If both HTML and Text exist, → the system sends a **Multipart Email**. |
| Recipient prefers **Email (HTML)** | Group prefers **SMS** | System sends **Email (HTML)** (recipient preference overrides group). |
| Recipient prefers **Email (Text)**, but HTML is also allowed | Group prefers **Email** | The system may send an **Email (HTML)**, because email formats are prioritized unless explicitly denied. |

## Related

- [Group Members: Read Mode](/edit-read-mode-window.md)
- [Group Creation: Sendout Options](/sendout-options-tab.md)