# Worker emails

{% hint style="info" %}
This functionality is available to customers on Business, Business Pro, and Enterprise plans.
{% endhint %}

You can interact with your workers via email. Each one of your worker has its own email address and inbox, which can be used to start work or provide input.

Your worker's email is its Custom URL + toolhouse.app. For example, if your worker's friendly name is `personal-assistant`, you can contact it at `personal-assistant@toolhouse.app`.

## Basic email rules

* Your worker can only accept emails when its visibility is set to Visible.
* Everyone who knows the worker's friendly name can send messages to it. You can add strict guardrails on who can interact with the worker using [Agent Editor](/toolhouse/toolhouse/agent-editor.md).
* The worker can reply if its email is in the To or Cc fields of your email. This is useful to Cc your worker on a conversation with others.
* The worker can read the entire email thread, but it does not read attachments.

## Set up the email name

1. Go to the [Agents page](https://toolhouse.app/agents)
2. Click on the worker you want to change.
3. Click <i class="fa-gear-complex">:gear-complex:</i> **Details.**
4. In the **Custom URL** section, type the address you want.

You can change your worker's address at any time. When you do so, you will make the old email available to other customers. Also keep in mind that we enforce these naming rules:

* Your worker's email can be 2-50 character long
* It can only contain lowercase letters, numbers, and dashes
* It cannot start or end with a dash
* It cannot contain profanity
* It cannot contain reserved words


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.toolhouse.ai/toolhouse/toolhouse/worker-emails.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.