# Automation

### Overview

MangoApps Automation makes it easy to set up automatic birthday and work anniversary messages for employees. These automations help foster a positive workplace culture by recognizing special occasions.

<figure><img src="/files/Bqz8lJubGRWrwYKBgvBV" alt=""><figcaption></figcaption></figure>

***

### Automations Menu

The Automations menu provides several options for managing automated messages.&#x20;

<figure><img src="/files/CH14OMzHWOpHEZtFOaxI" alt=""><figcaption></figcaption></figure>

#### Show

The Show menu allows you to filter and view different types of automation rules. You can choose from:

* **All:** Displays all created automations.
* **Anniversary:** Shows all workplace anniversary automations.
* **Birthday:** Lists all birthday automations.

***

#### Settings <img src="/files/24pd7ts2ArkqkoLcrh8c" alt="" data-size="line">

The **Settings** menu enables customization of the sender details for automated special occasion messages.&#x20;

<figure><img src="/files/fbL4sdVbFYy6gQvsmuyZ" alt="" width="532"><figcaption></figcaption></figure>

Change the sender's **Name** and **Picture** to personalize who the message appears to be from. By default, messages come from the "Happiness Manager" but can be customized so the sender appears as the head of HR, the CEO, or any other person.

Click **Save** once changes are made.

<figure><img src="/files/5FqiXwCevwjrITsrCdwF" alt="" width="372"><figcaption></figcaption></figure>

***

#### Add an Automation Rule

This option allows admins to create a new automation rule for birthdays or work anniversaries. Setting up a rule ensures timely and consistent recognition for employees on their special days.

<figure><img src="/files/5Inco8TVN7TKdZQbRQlb" alt="" width="563"><figcaption></figcaption></figure>

Create a new automation rule by selecting **Birthday** or **Anniversary** from the dropdown menu.

***

#### Toggle

The Toggle function lets admins enable or disable an automation rule within the domain without the need to delete it. This allows flexibility in managing which messages are currently active.

***

#### Three Dot Menu

The three-dot menu provides additional options for modifying automation rules:

* **Edit:** Modify the automation rules and behavior.
* **Delete:** Remove an automation rule (only available for creators or domain admins).

***

### Creating a New Automation Rule

Setting up a new automation rule ensures that birthday and anniversary messages are sent out automatically based on predefined conditions.&#x20;

To get started, click on **Add an Automation Rule** and select **For Birthday** or **For Work Anniversary.**

<figure><img src="/files/nd7S79BMmSorZx8FlCwt" alt="" width="563"><figcaption></figcaption></figure>

This will bring up the **Add Automation** window.

In this menu provide the following:&#x20;

* Provide a **Rule Name.**
* The trigger is set to run daily and **cannot** be changed.
* Set the **Condition** for when the message should be sent: Early Morning (5 AM - 9 AM), Late Morning (9 AM - 12 PM), Afternoon (12 PM - 4 PM), Early Evening (4 PM - 6 PM)
* Select the **Greeting Category** and either randomly select a greeting or assign a specific one for all users.

Click **Next** to continue.

***

### Story Collection

Story Collection is an optional feature that allows colleagues to send personalized messages along with the automated birthday or anniversary message. This adds a more personal and engaging touch to the recognition process.

<figure><img src="/files/iMlBHUerromo0erAOwxr" alt="" width="543"><figcaption></figcaption></figure>

Story Collection is optional and can be activated via a toggle.

<figure><img src="/files/UCtRJrIacLXkd9RXwWgB" alt="" width="563"><figcaption></figcaption></figure>

Choose when to send the Story Collection request:

* 2, 5, 10, or 15 days before the occasion.
* Select recipients of the private message:
  * **Direct Managers and Peers**
  * **Direct Reportees**
  * **Followers and Following Me**
* Customize the **Subject Line** and **Message Content**.
* Set a recipient limit between **10-50 users**.

Click **Save** to finalize the automation and Story Collection campaign.

{% hint style="info" %}

#### Message Distribution Priority

The system prioritizes recipients based on group selection and user activity. More active users are more likely to receive the message.
{% endhint %}

***

### Story Collection Reporting

Tracking the success of automated messages and Story Collection campaigns is essential for understanding engagement levels.&#x20;

Domain admins can generate reports to gain insights into user participation.

Navigate to the **Reports** module and select **Generate Report on Story Collection**. Choose the **Date Range** and click **Generate**.

<figure><img src="/files/NGm7Tbksr2J89Jm71SXv" alt="" width="563"><figcaption></figcaption></figure>

Access the report in the [**Generated Reports Folder**](https://guides.mangoapps.com/lms-guide/learn-admin/reports).

***

#### Report Contents

These reports provide a detailed breakdown of Story Collection performance, helping admins assess participation and response rates.&#x20;

<figure><img src="/files/h5K0BJPgnrw5SWLNf0ba" alt="" width="563"><figcaption></figcaption></figure>

The **Summary** tab includes insights such as Birthdays vs. Anniversaries and Stories Requested vs. Stories Received.&#x20;

The **Data** tab provides detailed metrics, including Rule Name, Rule Type, Story Requested On, Story Requested From, Story Request Count, Story Received Count, Scheduled For, and Scheduled On.


---

# Agent Instructions: 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:

```
GET https://guides.mangoapps.com/admin-guide/automation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.