> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/agency-permissions/setting-up-lead-delivery-and-review-alerts.md).

# Setting Up Lead Delivery & Review Alerts

## Setting Up Lead Alerts

1. On the Employee Admin home page, navigate to **Settings** > **Email Address**.
   1. Click **Create New.**
   2. Fill out the following information for the client-provided email.
      1. **Email Address:** Input the email address of the person who will be reviewing form submissions from your website.
      2. **Template**: Select "Lead", which will allow the form submission information to be sent over to you. 
2. Navigate to **Settings** > **Email Address** > **Lead Processing** button.
3. Click **Create New Lead Processor.**
   1. **Leads Intended For**: Leads can be specially routed for a Person, Facility or Markup. Most Customers just all leads sent to the same place - just choose the "Site" choice here.
   2. **Are Processed By**: Choose **DoctorLogic Email Delivery**
   3. **And Sent To**: Select the Email you added on step 1.
4. Click the Green Save icon ✅.

## Setting Up Review Alerts

1. On the Employee Admin page, navigate to **Settings** > **Email Address**.
2. Click **Create New.**
3. Fill out the following information for only the client email:
   1. **Email Address**: The email recipient of leads from forms filled out.
   2. **Template**: ReviewAlert.

{% hint style="info" %}
Recipients of the Review Alert emails receive a single email each week that summarizes details of the reviews that have come in for their site. It will include the total number of new reviews (subject line, header) and then a batched summary of all the reviews within the body of the email.
{% endhint %}

If you see a "<LeadTest@doctorlogic.com>" record already in place, don't delete or modify it. This is for testing and to ensure leads are flowing post go-live.&#x20;


---

# 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.doctorlogic.com/docs/agency-permissions/setting-up-lead-delivery-and-review-alerts.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.