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

# Email Marketing Integrations for Egentify: Klaviyo and Omnisend

> Send chat and ticket events into your Klaviyo or Omnisend automations, and give the AI agent commercial context about the customer it is talking to.

Egentify's AI agent handles customer support across chat, voice, and email, and those conversations are full of signals your marketing platform never sees. Someone adds a product to their cart from chat. Someone escalates a complaint. A ticket gets resolved. Connecting Klaviyo or Omnisend puts those moments into your automations.

> **[Klaviyo](https://egentify.com/docs/integrations/klaviyo.md)**
>
> Two-way. Sends chat and ticket events, and gives the agent customer context.

> **[Omnisend](https://egentify.com/docs/integrations/omnisend.md)**
>
> One-way. Sends chat and ticket events into your automations.

Both connect through a single click. Neither asks you to paste an API key.

## What gets sent

Egentify sends events, and for Klaviyo a small set of profile fields. All of them are named so they cannot collide with your own.

| Event | Klaviyo | Omnisend |
| - | - | - |
| Added to cart from chat | Yes | Yes |
| Product clicked in chat | Yes | Yes |
| Products shown in chat | Yes | No |
| Conversation escalated | Yes | Yes |
| Customer identified | Yes | No |
| Ticket created | Yes | Yes |
| Ticket resolved | Yes | Yes |
| Ticket updated or reopened | Yes | No |

On Klaviyo, ticket events also update profile fields for open ticket count, lifetime ticket count, last ticket status, last contact channel, and last contact date. Every one is prefixed so it sits apart from your own fields.

> [!NOTE]
>
> Events are queued instantly and delivered every five minutes, so allow up to five minutes before one appears in Klaviyo or Omnisend. Build your automations with that delay in mind.

## Choosing between them

| | Klaviyo | Omnisend |
| - | - | - |
| Sends chat and ticket events | Yes | Yes, a smaller set |
| Gives the agent customer context | Yes | No |
| Events for anonymous visitors | Yes, if you run Klaviyo's onsite script | No |
| Token expiry | Refreshes automatically | Never expires |
| Retries can double-fire an automation | No, events are deduplicated | Possible |

You can connect both. Unlike reviews, there is no one-provider limit here.

## Marketing consent

> [!WARNING]
>
> Egentify never subscribes anyone to marketing. It does not add people to lists or segments, and it does not set or change anyone's email or SMS consent. Consent comes from the places that ask for it, like your signup forms and your checkout opt-in, and it lives in Klaviyo or Omnisend.

Egentify does not create consent, but it does create triggers. If you build a flow on **Chat: Added to Cart**, it fires for everyone already subscribed who does that in chat. Worth deciding on purpose rather than discovering later.

Sending an event about someone who is not in your marketing platform yet creates a profile for them. That profile is not subscribed and cannot be emailed until they opt in somewhere else.

One thing to do on your side: chat activity now flows to a third party, so mention that in your privacy notice.

## Pausing versus disconnecting

**Toggling off** pauses the integration and keeps the connection. Events stop, and you can switch it back on whenever you want.

**Disconnect** removes the connection entirely and you will need to reconnect through the approval flow.

> [!WARNING]
>
> There is no email or in-app alert when a connection is lost. If events stop appearing in your marketing platform, check **Settings > Integrations** first.

## Who can set this up

Owners, admins, and Technical Specialists can connect, reconnect, and disconnect. Chat Supervisors see these settings in read-only form.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.