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

# In Call Email

> Let the agent send a prepared email during the call, using rules you write for when each one goes out.

**In Call Email** lets the agent email the person while still talking to them. Unlike
a text, the email is not written freehand. You prepare each one in advance and say
when it should be sent.

***

## Set it up

On the agent's **Basic Information** tab, click **In Call Email** under **Choose
Skills**.

First choose an **Email Provider**. The dialog shows whether the one you picked is
**Connected** or **Not Connected**, and lets you connect it without leaving the
page. See **[Google Workspace](/product/integrations/google-workspace)**
or **[Outlook](/product/integrations/outlook)**.

Then add one or more emails, using **+ Add email** for each extra one. Each has four
fields.

<Frame>
  <img src="https://mintcdn.com/fluents/Ntis-q5QWqwCqRQw/images/product/skills/in-call-email.png?fit=max&auto=format&n=Ntis-q5QWqwCqRQw&q=85&s=c655ed2b8931c94c57e38499d9a4f61a" alt="The Configure In Call Email dialog, showing the Email Provider with a Not Connected indicator, an Add email tab, and the four fields for each email" width="1231" height="975" data-path="images/product/skills/in-call-email.png" />
</Frame>

| Field                               | What it does                                         |
| ----------------------------------- | ---------------------------------------------------- |
| **When should this email be sent?** | The situation that should trigger it, in your words. |
| **From Email**                      | The address it comes from.                           |
| **Subject**                         | The subject line.                                    |
| **Body**                            | The content of the email.                            |

You can add several, each with its own trigger, and the agent picks the one whose
condition matches what happened on the call.

***

## Writing the trigger

The trigger is read by the agent, not by a rules engine, so write it as a plain
description of the situation. Something like "When user asks for product details".

The agent is told not to send anything unless a condition is met, and to use only the
details from the email whose condition matched. So a badly separated pair of triggers
is how you end up with the wrong email going out.

<Tip>
  Make your triggers clearly distinct from each other. Two that overlap leave the
  agent choosing between them, and it may not choose the way you expect.
</Tip>

***

## Personalising the body

The body can include placeholders that are filled from the call's context, so a
prepared email can still carry the person's name, an order number, or anything else
you passed into the call.

***

## The agent needs an address

The agent can only send if it has the person's email address. On an inbound call it
usually does not, so it will ask. If your flow depends on the email arriving, make
sure the agent has a reason to have collected the address by that point.

***

## Where to go next

* Send a text instead, which needs no address: **[In Call SMS](./in-call-sms)**
* Send something after the call rather than during it: **[Post-call](/product/features/post-call)**
* Everything else on the agent: **[Agents](/product/features/agent)**
