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

# Messages

> Run an internal agent on messages from Slack, Microsoft Teams, phone numbers, email addresses, WhatsApp numbers and website widgets, and choose whether it replies or just listens.

The **Messages** trigger runs an internal agent when a message arrives on a channel you choose. Use it for a team assistant in Slack, an agent that reads every message to a shared mailbox and files tasks, or a dedicated WhatsApp line your cleaners text status updates to.

Open the agent and select **Runs on > Messages**. The sidebar row shows how many channels the agent is on, or **Off** when it's on none.

## Slack and Microsoft Teams

Slack and Teams let your team call the agent from the chat tools they already use.

| Channel | Runs on | Before you start |
| - | - | - |
| **Slack** | Mentions and direct messages to your Conduit bot | [Connect Slack](https://docs.conduit.ai/setup/tools-and-integrations/connect-slack.md) |
| **Teams** | Mentions in the connected chat or channel | [Connect Microsoft Teams](https://docs.conduit.ai/setup/tools-and-integrations/connect-microsoft-teams.md) and connect a Teams chat or channel |

Turn on the switch for a channel to make the agent available there. With Slack on, @-mention your Conduit bot in a channel it's invited to, or send it a direct message, and ask Operator to hand the request off to this agent.

Turning a channel on takes effect right away. Turning one off asks you to confirm, because the agent stops being available from that channel.

## Phone, email and WhatsApp

The **Phone**, **Email** and **WhatsApp** sections list every phone number, email address and WhatsApp number in your workspace. Turn on the switch next to each one the agent should run on. Then choose how it responds there.

| Mode | What happens |
| - | - |
| **Reply** | The agent runs on each message and its answer is sent back in the same conversation. |
| **Listen only** | The agent runs on each message without an automatic reply. Its tools can still send messages. |

Use **Listen only** when the agent's job is to act on messages rather than answer them, such as tagging conversations, creating tasks or alerting your team. Use **Reply** when the agent should answer the sender directly, such as a cleaner texting a status update to a dedicated line.

### One replying agent per number or address

Only one agent can reply on each phone number, email address or WhatsApp number, so people never get two answers. Any number of agents can listen.

The builder warns you about overlaps:

| Warning | What it means | What to do |
| - | - | - |
| **Two agents reply here** | Another internal agent also replies on this number or address. | Set one of them to **Listen only**. |
| **Another agent may reply** | A customer agent may also answer messages here from its inbox. | Make sure the two agents won't both answer, or set this one to **Listen only**. |

When another agent already replies on a number or address, the **Reply** option names that agent and stays unavailable until you change it.

### Reply limits

To prevent loops and noise, a **Reply** agent doesn't send an automatic reply when:

* The message is an automated email, such as an auto-reply or a bulk mailing.
* The message is a delivery notification.
* The message comes from one of your workspace's own mailboxes.
* The agent has already sent 5 automatic replies in that conversation in the past hour.

The agent still runs on these messages, as if it were set to **Listen only**.

### Filter senders

You can limit which senders start the agent on a phone number, email address or WhatsApp number. Select the **More options** menu on a row that's turned on, then select **Filter senders**.

| Option | Who reaches the agent |
| - | - |
| **Everyone** | Every sender. |
| **Only these** | Only the numbers, addresses or domains you list. |
| **Everyone except** | Every sender except the ones you list. |
| **Custom** | Senders that match rules you build. |

For email, enter full addresses such as `name@example.com`, or a domain such as `@example.com` to match everyone at that company. For phone and WhatsApp, enter numbers with their country code, such as `+14155550100`.

**Custom** opens a rule builder. Combine rules with **All of** or **Any of**, group them, and use **Not** to invert a group.

Once a filter is set, the row shows a short summary of it.

## Website widget

The **Widget** section lists your website chat widgets. Turn on a widget to run the agent on messages sent through it. Widgets have no reply mode or sender filter.

To change how the agent replies in the widget, such as streaming its answer word by word, use **Widget overrides** on the agent's **Settings** tab. See [Agent settings](https://docs.conduit.ai/build-your-agent/agents/settings.md#widget-overrides).

## Messages that never start a run

The agent doesn't run on a message when:

* AI is paused on the conversation or the contact, and the agent is set to **Reply** there. **Listen only** agents still run while AI is paused, and their tools can still act, including sending messages.
* Conduit marks the message as spam.
* The sender doesn't match the row's sender filter.
* The agent is **Inactive**.


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