> ## 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.

# Mailchimp Voice AI Integration Guide

> Connect DialNexa voice AI with Mailchimp to update approved audience fields, tag confirmed interests, and respect email subscription choices.

The **Mailchimp voice AI integration** lets a confirmed call outcome improve audience data and follow-up relevance. It should never infer email consent from a conversation that did not clearly ask for it.

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

## When to use the Mailchimp voice AI integration

Use Mailchimp when:

* Marketing uses Mailchimp audiences, tags, and merge fields for follow-up.
* The caller confirms an interest, preference, or profile detail worth saving.
* Subscription status changes use explicit, recorded consent.
* Sales or support remains the owner of the full call record.

<Tip>
  **Best first workflow:** Match an existing audience member by verified email, update one approved interest field or tag, and store the call ID in your source system for traceability.
</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 Mailchimp 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 Mailchimp

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

## Build the Mailchimp 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 Mailchimp

* 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
* Mailchimp record ID, record URL, update timestamp, and integration result

## High-value Mailchimp voice AI workflows

| Call outcome                        | Mailchimp result                                    | Human control                              |
| ----------------------------------- | --------------------------------------------------- | ------------------------------------------ |
| Caller confirms a product interest  | Add an approved tag or merge-field value            | Use only explicit call answers             |
| Existing subscriber updates details | Update verified audience fields                     | Confirm email ownership first              |
| Caller asks to stop emails          | Route or apply the unsubscribe request              | Record the request and honor it promptly   |
| Lead asks for information           | Start an approved follow-up only with valid consent | Avoid duplicate or conflicting automations |

## Verify the Mailchimp integration

Run a test call and confirm that:

1. The verified email matches the intended audience member.
2. Only approved tags, merge fields, or interests change.
3. Subscription and unsubscribe actions have explicit, traceable consent.
4. The DialNexa call ID prevents duplicate follow-up triggers.
5. Cleaned, archived, ambiguous, or failed records create a review task.

## Troubleshoot Mailchimp integration issues

| Problem                                 | What to check                                                                                                                                     |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Mailchimp 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                                                                    |
| Audience member is not found            | Confirm audience, normalized email, member status, and whether the address is archived or cleaned                                                 |
| Duplicate follow-up starts              | Use the DialNexa call ID as an idempotency key and check current tags and automation state                                                        |
| 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)