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

# Brevo Voice AI Integration Guide

> Connect DialNexa voice AI with Brevo to update contacts, send approved transactional follow-ups, and manage consent-aware campaign routing.

The **Brevo voice AI integration** connects call outcomes with contact data and approved email or messaging follow-up. Separate transactional confirmations from marketing messages so consent and delivery rules remain clear.

<Warning>
  A catalog page describes a possible workflow. It does not confirm that a native Brevo connector is enabled in your workspace. Check **Integrations** in the DialNexa dashboard first. If Brevo is not listed, use a custom function, agent webhook, or external automation service.
</Warning>

## When to use the Brevo voice AI integration

Use Brevo when:

* A caller needs a booking, enquiry, or service confirmation after the call.
* Contact attributes or lists drive relevant follow-up.
* Transactional and marketing senders, templates, and consent rules are distinct.
* Delivery failures create a fallback task.

<Tip>
  **Best first workflow:** Send one approved transactional confirmation after a verified outcome, then store the message ID and delivery result with the call record.
</Tip>

## Before you begin

Prepare the following:

* A published DialNexa agent that has already passed a basic test call.
* Access to the DialNexa workspace **Integrations** page.
* A Brevo account with permission to read or update the required records.
* One test record that does not affect a live customer.
* A list of actions that can run automatically and actions that require human review.

## Choose how to connect Brevo

| Connection method                                   | Use it when                                             | Important limit                                                             |
| --------------------------------------------------- | ------------------------------------------------------- | --------------------------------------------------------------------------- |
| Workspace connector                                 | Brevo appears in your DialNexa **Integrations** page    | Available actions and authentication depend on your workspace               |
| [Custom function](/docs/agent-settings/custom-functions) | The agent needs Brevo data during the live conversation | Keep the request fast and return only the fields the agent needs            |
| [Agent webhook](/docs/api-access/agent-webhooks)         | Brevo should receive a result after the call            | Your endpoint must authenticate, retry safely, and prevent duplicate writes |
| External automation                                 | The workflow spans Brevo and several other systems      | Monitor the external workflow separately from the DialNexa call             |

## Build the Brevo voice AI workflow

1. Define the exact event that starts the action, such as a confirmed booking, qualified lead, support escalation, or completed call.
2. Choose the connection method from the table above.
3. Map caller identity, the DialNexa call ID, the verified outcome, and the destination record ID.
4. Add a condition so uncertain, sensitive, destructive, or high-value changes go to a human-owned queue.
5. Store the destination record URL or ID with the call result so your team can trace the handoff.
6. Test success, no-match, duplicate, permission-error, and timeout cases before using live traffic.

## Data to map between DialNexa and Brevo

* DialNexa call ID, call direction, status, and final outcome
* Caller name, phone number, email, and matched customer or account ID
* Structured fields collected during the call, including consent where required
* Short operational summary, requested next step, owner, and due date
* Transcript or recording link only when your privacy policy allows it
* Brevo record ID, record URL, update timestamp, and integration result

## High-value Brevo voice AI workflows

| Call outcome                    | Brevo result                                | Human control                              |
| ------------------------------- | ------------------------------------------- | ------------------------------------------ |
| Booking or request is confirmed | Send the approved transactional message     | Confirm recipient and template variables   |
| Contact confirms an interest    | Update an approved attribute or list        | Require marketing consent where applicable |
| Contact opts out                | Apply or route the request                  | Keep suppression changes traceable         |
| Message bounces or fails        | Record the event and create a fallback task | Do not repeatedly retry invalid recipients |

## Verify the Brevo integration

Run a test call and confirm that:

1. The verified recipient, sender, template, and dynamic values are correct.
2. Transactional and marketing messages use the appropriate consent and sender rules.
3. The DialNexa call ID prevents duplicate sends or automation triggers.
4. Message ID and delivery result are stored with the business record.
5. Bounce, block, unsubscribe, and failed-send events create the correct fallback.

## Troubleshoot Brevo integration issues

| Problem                             | What to check                                                                                                                                     |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Brevo is not shown in the dashboard | Use a custom function, webhook, or external automation service, or [request the integration](/docs/dashboard-integrations/requesting-new-integrations) |
| Authentication fails                | Reconnect the account and verify scopes, workspace ownership, and token expiry                                                                    |
| Contact or message is not found     | Confirm normalized recipient, list, template, sender, and returned message ID                                                                     |
| Duplicate messages appear           | Use the DialNexa call ID as an idempotency key and make retries safe                                                                              |
| The live call becomes slow          | Move nonessential writes to a post-call webhook and keep live lookups small                                                                       |

## Related pages

* [DialNexa integrations overview](/docs/integrations/overview)
* [Connect dashboard integrations](/docs/dashboard-integrations/connecting-integrations)
* [Use integrations in agents](/docs/dashboard-integrations/using-integrations-in-agents)
* [Use integrations in workflows](/docs/dashboard-integrations/using-integrations-in-workflows)
* [Integration workflow tutorials](/docs/tutorials/integration-workflows)