---
title: "Email"
url: "https://help.magicblocks.ai/en/article/email"
language: "en"
last_updated: "2026-03-18T08:22:47.274Z"
---

# Email

Once your AI Agent is live on your website, **Email** becomes one of the most powerful tools for turning conversations into conversions.

While the **Go Live** section itself focuses on embedding and deploying your Agent, **Email** works alongside it — ensuring that every interaction your Agent has on your live site is followed up, tracked, and transferred to the right people automatically.

## **What This Article Covers**

-   How Email connects to your Go Live Agent
-   How Email works *after* you Go Live
-   Common Go Live + Email workflows
-   How to use Email to follow up with live contacts

## How Email Connects to Go Live

When you **Go Live**, your Agent starts real conversations with real visitors on your website.  
Every chat, form, and goal completed on your live Agent can trigger an **email notification or follow-up**, powered by your existing **Actions** and **Contact Transfer** setup.

So while the **Go Live tab** manages your *embed* and *appearance*, the **Email logic** lives inside:

-   **Journey Actions** (e.g., “Send Email” or “Notify Team”)
-   **Contact Transfer Automations** (e.g., send form submissions to your inbox)

That means once your Agent is live, email isn’t something you configure inside “Go Live” — it’s something that *activates automatically* through your live triggers.

## Where Email Fits in the Live Workflow

Here’s how Email interacts with a live Agent after embedding:

| Step | Feature | What Happens |
| --- | --- | --- |
| 1 | **Agent is embedded** | The AI chat widget is active on your site. |
| 2 | **User chats with the Agent** | The Agent engages in real-time using your Persona + Journey. |
| 3 | **User submits a form or goal is reached** | A contact or conversion event is triggered. |
| 4 | **Contact Transfer fires** | MagicBlocks sends the captured info to your CRM or inbox. |
| 5 | **Email is sent automatically** | You (and/or the contact) receive an email notification or confirmation. |

### Example Use Case

**Scenario:** You’ve gone live with your “Epic Intros” Agent.  
Here’s how email fits into your real-world flow:

A visitor lands on your website.

Your Agent engages with a warm greeting (“Hook” block).

They show interest and fill out a “Get in Touch” form.

Behind the scenes:

The C**ontact Transfer** action fires.

MagicBlocks automatically emails your sales team:

> “New contact captured from Epic Intros — check CRM.”

Optionally, a confirmation email is sent to the user:

> “Thanks for reaching out! We’ll get back to you soon.”

The conversation ends — but the relationship continues via email.

## Email Options that Work with Go Live

### 1\. **Team Notifications**

Notify your internal team every time a contact is captured or a goal is met.  
Use this to alert your sales, support, or marketing staff instantly when your live Agent generates results.

Example:

> Subject: “New Demo Request from Website Chat”  
> Body: “A user named Alex booked a demo through your AI Agent on epicintros.vip.”

### 2\. **User Confirmation Emails**

Keep your prospects engaged after the chat ends by sending them automatic thank-you or follow-up messages.

Example:

> “Hey Alex, thanks for booking a call! One of our team members will reach out soon.”

### 3\. **CRM or Platform Notifications**

If you’ve connected your CRM (via Zapier or Webhooks), MagicBlocks can automatically trigger an email from your CRM system whenever your live Agent sends data over.

This means:  
You don’t have to send emails *from* MagicBlocks directly — it can hand the data to your CRM or marketing platform (like HubSpot, Pipedrive, or Mailchimp), which sends the email.

## How to Connect Email Workflows Before Going Live

To make sure your live Agent can send or trigger emails correctly:

Go to **General → Actions**.

Add an **Action** (e.g., “Send Email,” “Trigger Webhook,” or “Send to CRM”).

In your **Journey Blocks**, attach that action to your final stage — like *Get in Touch* or *Book a Demo.*

Test it using **Try My Agent** before publishing.

Then, go to **Go Live → Embed** and deploy the Agent.

Once live, the same actions will fire in real-time for real users.

### Key Difference: Go Live vs Email Logic

| Feature | **Go Live** | **Email (via Actions & Contact Transfer)** |
| --- | --- | --- |
| **Purpose** | Publishes your Agent on your site | Delivers notifications and confirmations |
| **Configuration Location** | *Go Live → Embed code, widget style* | *General → Actions / Contact Transfer* |
| **When It Runs** | When the Agent is loaded and visible | When a trigger or goal completes |
| **Result** | Active chat widget | Sent emails, team alerts, CRM sync |

*In short:*  
**Go Live puts your Agent on your site.**  
**Email keeps the conversation going afterward.**

## Best Practices

-   Always test email triggers before publishing your Agent.
-   Use professional “From” addresses for all client-facing emails.
-   Combine **Email + Contact Transfer** to automate both internal and external follow-ups.
-   Track conversions in **Measuring → Goals** to confirm email-triggered results.
-   Update your **Journey Actions** if you rebrand or change your domain.

## **Why It Matters**

A live Agent without follow-up is just a chat.  
By integrating **Email** into your Go Live setup, you:  
✅ Ensure instant human follow-up  
✅ Build trust and continuity after each chat  
✅ Close the loop between AI engagement and real-world conversion

## **Related Articles**

[Go Live Overview](https://help.magicblocks.ai/en/article/overview)

**Contact** [**Transfer Overview**](https://help.magicblocks.ai/en/article/leads-overview)

[Actions in Journey Blocks](https://help.magicblocks.ai/en/article/journey-actions)