> ## Documentation Index
> Fetch the complete documentation index at: https://docs.avidra.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Notifications

> Control how operators are alerted about new leads, emergencies, summaries, and AI-related events.

Notifications control how Avidra alerts your team about recovered leads, urgent conversations, and system events.

## What you configure

| Setting                    | Purpose                                                              |
| -------------------------- | -------------------------------------------------------------------- |
| Email notifications        | Receive lead and event alerts by email                               |
| Notification email address | Where email alerts are delivered                                     |
| SMS alerts                 | Receive alerts by text message                                       |
| Notification phone number  | Where SMS alerts are sent                                            |
| Notification frequency     | How often alerts are batched or sent                                 |
| Emergency alerts           | Immediate alerts for urgent conversations (e.g., gas leak, flooding) |
| Daily summary email        | Recurring digest of workspace activity                               |
| AI failure alerts          | Notifications when AI encounters errors                              |

## Why notifications matter

Without notifications, your team only learns about leads when they open the dashboard. That means urgent leads can sit for hours before anyone takes action.

Notifications determine whether your team learns about:

* **Newly recovered leads** that need follow-up — within minutes, not hours
* **Urgent or emergency conversations** — gas leaks, flooding, electrical hazards
* **Failures in AI or message handling** — threads that silently stopped working
* **Summary activity over time** — daily digests to spot trends

<Warning>
  If you rely only on the dashboard without notifications, urgent leads may go hours without a response. Always set up at least one alert channel.
</Warning>

## Recommended setup

<Tabs>
  <Tab title="Solo operator">
    You are the only person managing leads:

    * Enable **SMS alerts** to your personal phone
    * Enable **emergency alerts** for immediate escalation
    * Enable **daily summary email** to your inbox
  </Tab>

  <Tab title="Small team">
    Multiple people handle calls and follow-up:

    * Enable **email notifications** to a shared inbox (e.g., [leads@yourbusiness.com](mailto:leads@yourbusiness.com))
    * Enable **SMS alerts** to the on-call phone number
    * Enable **emergency alerts** to the team lead
    * Enable **daily summary** to the business owner
  </Tab>
</Tabs>

## What to monitor

Check notifications if:

* Leads are visible in the dashboard but nobody was alerted
* Emergency workflows did not reach the team
* AI failures are happening silently
* Summaries are going to the wrong destination

## Common mistakes

* Enabling notifications without entering a valid destination — alerts go nowhere
* Using an unmonitored phone or email address
* Disabling alerts and assuming dashboard review alone is enough for urgent leads
* Not testing notifications after initial setup — send a test to confirm delivery

## Related pages

<CardGroup cols={3}>
  <Card title="Business Hours" icon="clock" href="/configuration/business-hours">
    Set open hours and after-hours messaging.
  </Card>

  <Card title="Follow-up Automation" icon="repeat" href="/configuration/follow-up-automation">
    Automate second-touch messaging.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/support/troubleshooting">
    Diagnose notification issues.
  </Card>
</CardGroup>