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

# Notifications

> Getting your team alerted by email or SMS about workspace activity.

Notifications keep your team in the loop without anyone sitting in the dashboard. They're configured once for the whole workspace, under **Settings**.

## How it's set up

Two independent channels, each with its own recipient list and its own on/off switch:

| Channel   | You provide                 | Turn on with               |
| --------- | --------------------------- | -------------------------- |
| **Email** | One or more email addresses | Enable email notifications |
| **SMS**   | One or more phone numbers   | Enable SMS notifications   |

Both are off by default. Turning a channel on with an empty recipient list does nothing — add the addresses first.

<Note>
  Recipients are workspace-level, not per user. Anyone on the list gets notified whether or not they have a Recepta.ai login — useful for an owner or dispatcher who doesn't work in the dashboard.
</Note>

## Choosing recipients

<Columns cols={2}>
  <Card title="Use a shared address" icon="circle-check">
    Something like `office@` or a distribution list survives staff changes. A personal address stops being read the day that person leaves.
  </Card>

  <Card title="Keep the SMS list short" icon="mobile">
    Text alerts interrupt. Reserve them for the one or two people who need to act immediately, and leave everyone else on email.
  </Card>
</Columns>

<Warning>
  SMS notifications go out over the same [A2P-registered](/phone/a2p-10dlc) messaging as your customer texts. If your registration isn't approved yet, internal SMS alerts won't be delivered reliably either.
</Warning>

## Keep the billing address monitored

Separate from these settings, billing notices go to your billing contact — and this is the one that catches people out.

<Warning>
  A failed payment eventually suspends service, and a suspended workspace stops answering your phone. If billing notices are going to someone who has left the business, nobody sees the warnings. Check the address on your [billing](/account/billing) settings is one a person actually reads.
</Warning>

## Building your own alerting

If you want alerts inside your own tools — a Slack channel, a dispatch board, an on-call system — use [webhooks](/api-reference/webhooks) rather than email. Subscribe to the events you care about and route them wherever your team already works:

| Event                   | Useful for                            |
| ----------------------- | ------------------------------------- |
| `call.human_escalation` | Paging whoever is on call             |
| `call.ended`            | Posting a call summary into a channel |
| `sms.received`          | Alerting on inbound customer texts    |
| `contact.created`       | Notifying sales of a new lead         |

That gives you routing, filtering, and escalation logic that a recipient list can't.