Skip to main content

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

Open the channel configuration

1

Go to Channels

In the side panel open Channels and find the Email channel in the list.
2

Open the channel

Click the channel. The edition view opens with its current configuration.

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

Reply signature

Defines the name replies from the channel are signed with:

Ticket expiration

The hours of inactivity after which a ticket closes automatically. Closing triggers the channel’s close flow.
Expiration counts from the ticket’s last message, not from its creation.

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.
Blocking is silent: the sender gets no notice that their message was discarded. Don’t use it for real customers.

What you cannot edit

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

Check the channel is ready

The channel view shows its readiness status with the warnings that prevent it from working correctly:
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.

Next step

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.