> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/designer/notifications-and-communications/turning-on-notifications-for-communications.md).

# Turning On Notifications for Communications

## Overview

When a patient sends a message (SMS, email, or chat), Welkin can notify care team members in real time. This page explains how to configure communication-related notifications in the Designer so that the right people are alerted when patient messages arrive.

***

## How Communication Notifications Work

When a patient sends a message:

1. The message arrives in the Inbox (or legacy communication center).
2. If notification rules are configured, the system sends an alert to the designated recipient(s).
3. The recipient clicks the notification to open the communication.

The Admin Portal controls where notification clicks route users – to the new Inbox or the legacy communication center. See [Admin Portal Overview](https://docs.welkinhealth.com/admin) for details.

***

## Configuring Communication Notifications in the Designer

1. In the Designer, navigate to **Notifications**.
2. Click **+ Add Notification** or edit an existing one.
3. Set the **trigger** to a communication event:
   * "Incoming SMS received"
   * "Incoming email received"
   * "Incoming chat message received"
4. Define **recipients** – typically the assigned care team member or primary contact.
5. Choose **delivery channels** – in-app, email, or both.
6. Save and publish.

***

## Admin Portal: Inbox Notification Routing

In the Admin Portal under **Feature Settings → Environment → Inbox Notifications**:

* **Enabled** – clicking a notification opens the new Inbox
* **Disabled** – clicking a notification opens the legacy patient-level communication center

See [Inbox](https://docs.welkinhealth.com/care/communication/inbox) for the full Inbox guide.

***

## Publishing

Create a draft in the Designer and publish to apply notification configuration changes.


---

# 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://docs.welkinhealth.com/designer/notifications-and-communications/turning-on-notifications-for-communications.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.