# Notifications and Alerts ## Overview Welkin's notification system keeps care team members informed of important events — including new patient messages, upcoming encounters, task due dates, and workflow triggers — without requiring constant manual checking. ## Types of Notifications ### In-App Notifications Notifications appear as a badge on the bell icon in the top navigation bar. Click the bell to view a list of recent notifications. Each notification links directly to the relevant record or action. ### Email Notifications Welkin can send email notifications to care team members for: * New inbound patient messages * Upcoming encounter reminders * Task assignments or due dates * Automation-triggered alerts Email notifications are configured by your administrator in Welkin Designer. ### Automated Notifications Automations configured in Designer can send notifications to care team members when specific conditions are met — for example, when a patient's assessment score changes or when a patient enters a new program phase. See [Automated Notifications](https://github.com/welkincloud-io/welkin-docs/blob/master/kb/designer/automated-notifications.md) for configuration details. ## Managing Notifications To review or clear notifications: 1. Click the **bell icon** in the top navigation 2. Notifications are listed in reverse chronological order 3. Click a notification to navigate to the relevant record 4. Mark notifications as read individually or use **Mark All as Read** ## Notification Volume If you are receiving too many notifications, contact your administrator to adjust automation-triggered notifications for your role in Designer. --- # 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://docs.welkinhealth.com/care/getting-started/notifications-and-alerts.md?ask= ``` 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.