> For the complete documentation index, see [llms.txt](https://docs.senpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.senpiper.com/alarm-builder/setting-up-an-alarm/add-new-alarm/defining-the-communication-type.md).

# Defining the communication type

## 1. Selecting the type of communication

There are three types of communication that can configured for alerting the users:

1. [**Email**](/alarm-builder/setting-up-an-alarm/add-new-alarm/defining-the-communication-type/send-an-email.md)
2. [**SMS**](/alarm-builder/setting-up-an-alarm/add-new-alarm/defining-the-communication-type/send-an-sms.md)
3. [**App Notification**](/alarm-builder/setting-up-an-alarm/add-new-alarm/defining-the-communication-type/send-an-app-notification.md)

We need to select the type of alert that you want to configure.&#x20;

## 2. Selecting the receivers for your alerts

Once we select the type of alert to be configured, we need the select specific users or roles who are to receive the alert.

Learn more about selecting the receivers for [**email**](/alarm-builder/setting-up-an-alarm/add-new-alarm/defining-the-communication-type/send-an-email.md#selecting-the-receivers-for-your-email), [**SMS** ](/alarm-builder/setting-up-an-alarm/add-new-alarm/defining-the-communication-type/send-an-sms.md#selecting-the-receivers-for-your-sms)and [**app**](/alarm-builder/setting-up-an-alarm/add-new-alarm/defining-the-communication-type/send-an-app-notification.md#selecting-the-receivers-for-your-app-notification) alerts.

## 3. Setting a condition for your alerts

We can configure a **condition in which when met**, the **communication will be triggered** and the **alert will be sent to the selected users**.&#x20;

{% hint style="info" %}
If no condition is set, the alert will be sent every time the alarm is triggered.
{% endhint %}

1\.   To configure a condition for alert, under **Communication Conditions**, click **Set condition.** The **Set condition** window is displayed.&#x20;

![](/files/6cYByKw7SAzaOVeH36oj)

2\.   Click **Add rule,** enter the condition as required, and then click **Apply**.

<figure><img src="/files/F3U3wl89nFjSJxXaaaoV" alt=""><figcaption><p>Adding Conditions </p></figcaption></figure>

To configure more alerts, click **Add Another Condition** at the bottom left of the right pane.

<figure><img src="/files/SlEENaevANx9nRFcDen1" alt=""><figcaption><p>Add another Communication</p></figcaption></figure>

After you've filled in the required details, on the bottom right of the screen, click **Next**. \
In the Step 3 screen, the **Define schedule** is displayed.


---

# 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://docs.senpiper.com/alarm-builder/setting-up-an-alarm/add-new-alarm/defining-the-communication-type.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.
