> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/messaging-features/automated-messaging.md).

# Automated messaging

Automated messages run continuously on user actions or a recurring schedule once trigger and timing are set.

Automated Messages let you send messages based on **user actions** (events) or a **schedule**. You configure the trigger and timing once, then Netmera runs it continuously.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FdGuBp0dmtXhWJ4oGLM0f%2Fimage.png?alt=media&#x26;token=70a233c0-061a-4e28-b8e0-8e40f2aa1ef4" alt="" width="563"><figcaption></figcaption></figure>

**Path:** `Messages > Automated > Create New Automated Message`

{% hint style="info" %}
**Quick steps**

1. Choose a type: [User Action](#user-action) or [Periodic](#periodic).
2. Configure trigger events and timing.
3. Configure limits and time restrictions.
4. Create content in **Setup, What, Who, Go**.
5. Launch the automation.
   {% endhint %}

{% @arcade/embed url="<https://app.arcade.software/share/rbkalY98lwHUXEZ0Kq0z>" flowId="rbkalY98lwHUXEZ0Kq0z" %}

### Option 1: User Action <a href="#user-action" id="user-action"></a>

User Action automations trigger from user events. You define the event logic and the timing window.

#### Increase Retention <a href="#increase-retention" id="increase-retention"></a>

Trigger a message after a user performs (or doesn’t perform) an event. This is the simplest event + delay flow.

**Setup**

* Select the trigger in **Event**.
* Define the delay in **Period**.
* Choose device scope:
  * **Send message to all devices of user**
  * **Send message to last used device of user**

<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKVrYQPrAxXrP0zWJer6d%2Fuploads%2FIgM2qlfcf3RoCpd8Urvw%2Fimage.png?alt=media&#x26;token=d85f2ea6-fdfe-4bec-835d-3d26b616d6bd" alt="" width="563"><figcaption><p>Increase Retention</p></figcaption></figure>

#### Increase App Conversion <a href="#increase-app-conversion" id="increase-app-conversion"></a>

Use push notifications to re-engage customers who haven't returned after a purchase by offering exclusive deals. For users yet to purchase, highlight the benefits of your product or service to encourage them to buy.

Trigger a message when users complete **Event 1** but do not complete **Event 2** in time. This is built for drop-offs and funnel conversions.

**Setup**

* Select **Event 1** and **Event 2**.
* Optionally add **Event 3** with **OR** logic to Event 2.
* Choose timing:
  * **Period** for a rolling window, or
  * **Time Specific** for start/end/send time.

{% hint style="success" %}
**Retention vs Conversion**

* **Increase Retention**: single event + follow-up delay.
* **Increase App Conversion**: event sequence + missing-event logic.
  {% endhint %}

<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKVrYQPrAxXrP0zWJer6d%2Fuploads%2FlojunepqN4lrlU5dFEQr%2Fimage.png?alt=media&#x26;token=64309d2d-3480-4fc2-811f-6fbdeee4adc5" alt="" width="563"><figcaption><p>Increase App Conversion</p></figcaption></figure>

#### Handle Special User Action <a href="#handle-special-user-action" id="handle-special-user-action"></a>

To handle special user actions, you can set up automated push notifications based on the **frequency of certain actions**, such as sending a message when a user makes a second in-app purchase. Trigger a message when an event happens **N times** in a time window.

**Setup**

1. Select the trigger in **Goal**.
2. Set the event count in **Occurrence**.
3. Define the window in **Capture Events in**.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F4haGRXYENSshMSSekrhE%2Fimage.png?alt=media&#x26;token=8ceabd6d-2440-4f72-910c-869800ca876b" alt="" width="563"><figcaption><p>Handle Special User Action</p></figcaption></figure>

#### Merge Events <a href="#merge-events" id="merge-events"></a>

Create automation scenarios that trigger a single set of actions when multiple events occur in a specific order. In the event type section, you select the events and event attributes that you want to track, and then assign a desired event key to each event.

Trigger a single automation when multiple events happen in a specific order. Use **Context** to pass values into the message for personalization.

**Setup**

1. **Goal**: select events and event attributes. Assign an event key per event.
2. **Timing**: define ordering rules and time windows.
3. **Fallback**: define what happens if the sequence is not completed in time.
4. **Context**: map event keys to message attributes.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F83Tks7qgXwAhpGDU4mbz%2Fimage.png?alt=media&#x26;token=23e842d8-f732-4733-9bdd-ff21ce7b66f2" alt="" width="563"><figcaption><p>Merge Events</p></figcaption></figure>

**Timing options**

* **Events must be captured in the specified order**
* **Capture events in** (time allowed for the next step)
* **Send a message if event(s) is not captured in the chosen period** (fallback path)

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FM1mhBhDPvEBPDXhklRnZ%2Fimage.png?alt=media&#x26;token=ec60af7f-0fb5-4931-9789-fe2cfd56465c" alt="" width="563"><figcaption><p>Merge Events - Timing</p></figcaption></figure>

**Context**

Event Key values serve as attributes, while parameters, indicated by their **Param Value**, establish the Merge Event's context. This enables personalized and specific message creation within the content section.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FYbTMpUAU2VT2vF1GXDbn%2Fimage.png?alt=media&#x26;token=1afc6a0b-08e5-4abe-b376-130a3bce6d09" alt="" width="563"><figcaption><p>Merge Events - Context</p></figcaption></figure>

### Option 2: Periodic Messages <a href="#periodic" id="periodic"></a>

Periodic messages are messages that are sent **regularly on a scheduled basis**, such as daily, weekly, or monthly. These messages can be set up to be sent at a specific time, ensuring that they reach the user at a time when they are most likely to engage with them.

Periodic automations run on a fixed schedule. You can set them up as **daily**, weekly, or monthly. Use them for recurring messages like birthdays or newsletters.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FHI0zgHSSyq8Pifc5sqkS%2Fimage.png?alt=media&#x26;token=26693f3f-4d57-496d-b5b8-6d332a9fabcb" alt="" width="563"><figcaption><p>Periodic</p></figcaption></figure>

#### Weekly schedule

Select one or more days of the week.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FrCvdvNdf9Wneq48bRykv%2Fimage.png?alt=media&#x26;token=24b65f49-99e4-4952-9b50-8b4626c2286e" alt="" width="563"><figcaption><p>Weekly</p></figcaption></figure>

#### Monthly schedule <a href="#monthly-schedule" id="monthly-schedule"></a>

Under **Monthly**, use **Repeat By** to choose how the monthly schedule is defined. **Day of Week** is selected by default.

* **Day of Week**: select a pattern like “first Monday” or “third Friday”.
* **Day of Month**: select one or more calendar days, such as the 1st and 15th of each month.

If you switch between **Day of Week** and **Day of Month**, the selections made in the other option are cleared. Monthly automations that use **Day of Week** keep working as before.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2Fsf9SJnBKe2YguCrsT3Y6%2Fimage.png?alt=media&#x26;token=55e4cc3d-aebc-4986-82e7-20dd5a7a0ac9" alt="" width="563"><figcaption><p>Monthly</p></figcaption></figure>

#### Day of Month <a href="#day-of-month" id="day-of-month"></a>

Use **Day of Month** for messages tied to a calendar date, such as payday offers, statement reminders, or bill due-date reminders.

1. Select **Monthly**, then set **Repeat By** to **Day of Month**.
2. Under **Select Days**, select one or more days from `1` to `31`. Click a selected day again to clear it. Your selection is listed under **Selected Days**.
3. Optionally select **Last Day of Month** to always send on the final day of each month (for example, February 28 or 29, April 30, January 31). You can also select **Last Day of Month** on its own.
4. In **Repeat Every**, enter how many months pass between sends (`1`–`12`). The default is `1`. The count starts from the campaign's start month.
5. Set the **Send time**.

At least one day is required. If no day is selected, the automation is not saved and **Select at least one day.** is shown. If **Repeat Every** is outside `1`–`12`, **Enter a value between 1 and 12.** is shown.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FSM0BRAX8bzyNm7yMBT2z%2Fdoc-automated-dom-1.png?alt=media" alt="Monthly schedule with Repeat By set to Day of Month, days 8, 16, 27 and 31 selected, Last Day of Month checked and Repeat Every set to 1 month" width="563"><figcaption><p>Day of Month</p></figcaption></figure>

{% hint style="warning" %}
Days `29`, `30`, and `31` are skipped in months that don't have that date. The message is not moved to another day. To always reach the end of the month, select **Last Day of Month**.
{% endhint %}

The selected rule is shown in the **Scenario** column of the automated messages list, for example: *Send the message on 12, 13, 14, 19, Last Day of Month of every month at 11:00*.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2Fe3XMnzshTwn3aGmaCjBx%2Fdoc-automated-dom-2.png?alt=media" alt="Scenario column in the automated messages list showing a Day of Month schedule"><figcaption><p>Scenario summary</p></figcaption></figure>

### Campaign Period for User Action Notifications <a href="#campaign-period-for-user-action-notifications" id="campaign-period-for-user-action-notifications"></a>

Campaign Period controls how long the automation is active and how often it can send. This is where you configure scheduling for User Action automations.

#### Campaign Period <a href="#campaign-period" id="campaign-period"></a>

Defines the active period for the automation. Messages are sent only inside this window. Choose whether the scenario runs every time it matches, or only once.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FaxNoNeBXYduEZ5fqcqTJ%2FScreenshot%202025-01-09%20at%2015.59.53.png?alt=media&#x26;token=12150f87-a143-4b69-8f68-e41c01226e65" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Automated messages do not use a separate “When” step. Scheduling is configured inside the automation.
{% endhint %}

#### When selected scenario occurs, send message

Send every time or only once per user.

#### User Limit

Per-user cap in a time window. Controls how many times a single user can receive the same message within a specified period.

* Per Day: Limits the number of messages a user can receive in one day.
* Per Week: Restricts the number of times the user can receive the message in a week.
* Per Month: Prevents excessive messaging to a user within a month.
* Custom Month: Allows specifying the number of messages per a custom-defined time period (e.g., 3 messages per 6 months).

#### Total Limit

Overall cap across all users. Sets the overall cap on the number of messages sent across all users during the campaign.

* Total Message Count: A numerical limit that specifies the maximum number of messages to send during the campaign.

#### Message Limit

Cap on message volume across all users. Adds a layer of control to limit how frequently a particular message is sent overall, across all users.

* Per Hour: Restricts the message from being sent more than a set number of times in an hour.
* Per Day: Limits daily message volume.
* Per Week: Sets a weekly maximum for the message.
* Per Month: Prevents excessive messaging over a longer time period.

#### Message Expire In

Drop messages not delivered within the given time. Defines how long the message remains valid for delivery after being triggered.

* A numerical value and time unit (e.g., hours or days) indicating the expiration period.

You set the message to expire in **6 hours**. If the triggering condition occurs at 3 PM, the message won’t be sent to users after 9 PM.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2Fg535wsH34TjK0wyzS8bs%2FScreenshot%202026-01-13%20at%2015.08.46.png?alt=media&#x26;token=e28104e0-7f1f-4191-a758-2e24985a3248" alt="" width="563"><figcaption></figcaption></figure>

#### Push Time Restriction

Restricts which hours and days sending is allowed:

* Send Only Between: start/end time window.
* Send Only On: day-of-week selection.
* Delay the Push If Not Permitted: queue until allowed.
* Send Based on User’s Time Zone: evaluate windows per user.

#### Instant Show <a href="#instant-show" id="instant-show"></a>

Enables that a widget is displayed immediately upon the occurrence of the triggering condition. If, due to technical constraints, the widget cannot be displayed at the moment of the trigger, it will not reappear in subsequent sessions or on other screens.

#### Quiet Dates

Pauses the scenario on selected calendar dates.

* Sending is blocked for 24 hours on each Quiet Date.
* Evaluation follows the scenario’s time zone setting:
  * User Time Zone enabled: applied per user.
  * User Time Zone disabled: applied in project time zone.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FbgNJovVDUtNGNtaggpbp%2FScreenshot%202026-01-13%20at%2015.07.22.png?alt=media&#x26;token=5ec02176-15be-42d9-ae77-50b3f234e2a8" alt="" width="563"><figcaption></figcaption></figure>

#### Sending Queue

Use **Sending Queue** to place a message into a separate sending queue and define its order within that queue.

Messages without a queue value are sent immediately at the scheduled time. Messages with a queue value are processed only after all immediate messages are delivered.

The **Queue Order** value determines the order of the message within the queue. Lower numbers are processed first.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2Ff0KZHKYSVUvMXvhoVxJO%2Fimage.png?alt=media&#x26;token=7805111d-98b8-4a77-a88c-43dce1c942b3" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FSQiHbBViTCFeLmGw2CpK%2Fimage.png?alt=media&#x26;token=fc0ef114-38e1-4884-8ca7-050a046dab26" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Queue Order does not make a message higher priority than messages without a queue value. It only defines the message's order within the sending queue.
{% endhint %}

### Other steps

After automation is configured, complete the standard campaign steps.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://user.netmera.com/netmera-user-guide/messaging-features/automated-messaging.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
