> For the complete documentation index, see [llms.txt](https://help.leadboxer.com/leadboxer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.leadboxer.com/leadboxer/using-the-app/elements/notifications.md).

# Notifications

LeadBoxer can email you and your colleagues about your leads. There are three kinds of notifications.

## Segment notifications (daily or weekly)

Once you have created a [Segment](/leadboxer/using-the-app/elements/segments.md) you can have it emailed to yourself and your colleagues, for example a daily email with the top-ranked leads, or a weekly overview of all visitors from a list of target accounts.

For each segment you choose:

* **Email**: Daily, Weekly or Off
* **View**: send the Leads view or the Accounts view
* **Format**: HTML (in the body of the email), PDF or CSV
* **Recipients**: one or more users of your account

The alerts can be **very specific** (a particular company for account-based marketing, or a client viewing the pricing page) or **very broad** (a region, all identified companies, or one alert per industry).

You can see all your segments and their notification settings on the Segments page. See [How to create a notification](/leadboxer/guides/how-to-create-a-notification.md) for the steps.

## Report notifications (weekly or monthly)

A [Report](/leadboxer/using-the-app/reports.md) can be emailed on a schedule. Open the report, click the arrow next to **Export As PDF** to open the **Scheduled Report** options, turn on **Enable Notification**, pick **Weekly** (sent at the end of the week) or **Monthly** (sent at the end of the month) and add the recipients. The report is sent with the configuration it has when you save the notification.

## LeadBoard notifications

LeadBoard owners get an email when something changes on their cards. You can turn each of these on or off under **Settings > Notifications**:

* New LeadCard assigned to me
* LeadCard owner update
* LeadCard moved stage
* LeadCard was removed


---

# 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://help.leadboxer.com/leadboxer/using-the-app/elements/notifications.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.