> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/ai-voice-agents/how-to-set-up-your-ai-voice-agent/post-call-analysis-notifications.md).

# Post Call Analysis – Notifications 🔔

The **Notifications** feature lets your agent send an automated email after a call is executed. You decide who receives it, which post-call data the email contains, and the condition that must be met for the email to be sent.

Emails are sent from `notifications@daptatech.com`.

You'll find it in the **Post-Call Analysis** section of your agent, selectable from the **Call Analysis** tab within the voice agents, below **Call Analysis Flow**.

<figure><img src="/files/ZvHozVVAkV6bLVf4Ihs0" alt=""><figcaption></figcaption></figure>

If no notification has been configured yet, the card shows an **Add Notification** button. Once configured, the card displays the recipient and trigger condition, and it can be edited or deleted.

***

## Setting Up a Notification

Click **Add Notification** to open the configuration modal.

<figure><img src="/files/934rz6ZEdg2Sc4DLhdgC" alt=""><figcaption></figcaption></figure>

### Name

A label to identify this notification internally (e.g. *Sales follow-up alert*). Required.

### To

The email address that will receive the notification. Required, and must be a valid email.

### Body

Choose which post-call data the email includes. Each section is a toggle and all are enabled by default:

* **Call Details** – basic call metadata such as numbers, duration and timestamps.
* **Customer Information** – the customer details associated with the call.
* **Post Call Analysis** – the custom variables extracted during post-call analysis.

Turn off any section you don't want to receive.

### Send Condition

The send condition is **required**. The email is delivered only when the chosen post-call analysis variable matches a specific value.

* **Variable** – pick one of the variables you defined in **Data Retrieval from your Calls**.
* **Condition** – `Equals` or `Does not equal`.
* **Value** – the value to compare against. The input adapts to the variable type:
  * **Boolean** → choose *Yes* or *No*.
  * **Selector (enum)** → choose from the variable's predefined options.
  * **Text / Number** → type the expected value.

{% hint style="info" %}
The send condition depends on a post-call variable. If no post-call variable has been created and the condition is not set, the notification can't be sent. Define your variables first under **Data Retrieval from your Calls**. See [Post Call Analysis – Post-Call Data Retrieval](/ai-voice-agents/how-to-set-up-your-ai-voice-agent/post-call-analysis-post-call-data-retrieval.md).
{% endhint %}

We recommend creating a new post-call variable specifically as the trigger for the notification (for example a `successful_call` boolean, or a `should_notify` selector), so the condition stays meaningful and isolated from variables used elsewhere.

Example: send the email only when `successful_call` **equals** `Yes`.

### Send Email Test

Use **Send Email Test** to send a sample email to the configured recipient with the currently enabled sections, so you can preview the format before saving.

### Saving

Click **Confirm** to save. All three send condition fields (variable, condition, value) must be completed before saving. Use **Cancel** to close without saving.

***

## Editing or Deleting

From the Notifications card, use the **pencil** icon to reopen the modal and adjust any setting, or the **trash** icon to remove the notification (a confirmation is required). Only one notification can be configured per agent.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dapta.ai/ai-voice-agents/how-to-set-up-your-ai-voice-agent/post-call-analysis-notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.