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

# Manage the Email channel

> Edit the support teams, the signature, the ticket expiration and the blocked list of an Email channel that already exists.

## Introduction

Once the Email channel is created, its configuration is edited from the channel view without recreating it. This guide covers what can be changed, what effect each change has, and what cannot be modified.

<Note>
  Changes are applied to the connected bot, so they affect **new** tickets. Open tickets keep the team and the configuration they had when they were created.
</Note>

## Open the channel configuration

<Steps>
  <Step title="Go to Channels">
    In the side panel open **Channels** and find the Email channel in the list.
  </Step>

  <Step title="Open the channel">
    Click the channel. The edition view opens with its current configuration.
  </Step>
</Steps>

## What you can edit

### Support teams

Determines which teams the new tickets opened by the channel are assigned to.

* With **one team**, every ticket goes to that team
* With **several**, the ticket becomes available to the operators of those teams

<Warning>
  A channel with no teams configured opens tickets no operator sees in their inbox. If the channel shows no conversations, this is the first field to check.
</Warning>

### Reply signature

Defines the name replies from the channel are signed with:

| Option       | Result                                                    |
| ------------ | --------------------------------------------------------- |
| **Team**     | Replies are signed with the support team's name           |
| **Operator** | Replies are signed with the name of the operator replying |

### Ticket expiration

The hours of inactivity after which a ticket closes automatically. Closing triggers the channel's close flow.

<Note>
  Expiration counts from the ticket's last message, not from its creation.
</Note>

### Blocked addresses

A list of addresses whose mail the channel discards without opening a ticket. Useful for automated senders that create noise, such as system notifications or newsletters.

<Warning>
  Blocking is silent: the sender gets no notice that their message was discarded. Don't use it for real customers.
</Warning>

## What you cannot edit

| Field                    | Why                                                                                                                                           |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **Support address**      | It's the address the channel recognizes as its own. Changing it would leave open tickets pointing at an address the channel no longer handles |
| **Inbound address**      | Jelou provisions it when the channel is created and it's the one receiving the forwarding                                                     |
| **Brain Studio project** | The channel's logic lives in that project                                                                                                     |
| **Provider credentials** | They're stored encrypted and never shown again                                                                                                |

<Note>
  To change any of these fields you have to create a new channel and move the forwarding to its inbound address.
</Note>

## Check the channel is ready

The channel view shows its readiness status with the warnings that prevent it from working correctly:

| Warning                        | Severity | What it means                                                                                                                                                                          |
| ------------------------------ | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Dynamic events disabled**    | Blocker  | The company has dynamic events turned off, so closing a ticket won't trigger its close flow. The ticket still closes and the operator sees a success message, so the failure is silent |
| **Close event not configured** | Warning  | The channel has no close event of its own, so the default selected event is used                                                                                                       |
| **Teams not configured**       | Warning  | The channel has no teams, so tickets reach no inbox                                                                                                                                    |
| **Free-mail domain**           | Warning  | The sending address sits on a domain whose DNS you don't control, so delivery may fail                                                                                                 |

<Warning>
  The **dynamic events disabled** warning is the only blocker, and its failure leaves no trace: the operator closes the ticket, sees the success message, and the close flow never runs. If your channel must run logic on close, check this before publishing.
</Warning>

## Next step

* If you need to change how replies are sent: [Authorize sending from your domain](/en/guides/activacion-canales/email-dns) or [Verify an address without touching DNS](/en/guides/activacion-canales/email-verificacion)
* If the channel receives no mail: check the [forwarding from your mailbox](/en/guides/activacion-canales/email-reenvio)

<Tip>
  After changing the teams, send a test message and confirm the ticket shows up in the right team's inbox before considering the change done.
</Tip>