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

# Klaviyo Voice AI Integration Guide

> Connect DialNexa voice AI with Klaviyo to add verified customer events, update profiles, and improve ecommerce follow-up without consent drift.

The **Klaviyo voice AI integration** turns verified ecommerce call outcomes into profile fields or events that can guide follow-up. Send structured business facts, not raw transcripts, and keep marketing consent separate from call intent.

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

## When to use the Klaviyo voice AI integration

Use Klaviyo when:

* Ecommerce marketing uses Klaviyo profiles, events, segments, and flows.
* The call confirms an order concern, product interest, preference, or support outcome.
* One custom event has a documented schema and purpose.
* Flow entry and exit rules prevent irrelevant messages after the call.

<Tip>
  **Best first workflow:** Send one `Voice Call Completed` event with the call ID, verified outcome, order reference, and next step, then use a tightly scoped flow for the relevant outcome.
</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 Klaviyo 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 Klaviyo

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

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

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

## High-value Klaviyo voice AI workflows

| Call outcome                       | Klaviyo result                                    | Human control                                 |
| ---------------------------------- | ------------------------------------------------- | --------------------------------------------- |
| Customer confirms product interest | Add a structured event or approved profile field  | Do not infer consent from interest alone      |
| Support issue affects an order     | Add an event that suppresses unsuitable promotion | Keep support resolution in the support system |
| Customer asks to stop marketing    | Apply the approved consent process                | Make the change traceable                     |
| Call outcome is uncertain          | Store it only in the source system                | Do not trigger a marketing flow               |

## Verify the Klaviyo integration

Run a test call and confirm that:

1. The verified customer matches the intended Klaviyo profile.
2. The custom event name and properties follow the documented schema.
3. No transcript, unnecessary personal data, or unsupported inference is sent.
4. The call ID serves as the event's duplicate-protection key.
5. Flow entry, suppression, consent, and failed-event behavior match the test plan.

## Troubleshoot Klaviyo integration issues

| Problem                               | What to check                                                                                                                                     |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Klaviyo 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                                                                    |
| Profile or flow is not matched        | Confirm profile identity, event name, property schema, segment rules, and flow filters                                                            |
| Duplicate events appear               | Use the DialNexa call ID as the event's unique 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)