# Mail and shared mailboxes

Mail is where a team answers the email it receives at a shared address, such as sales@ or info@. Everybody in the mailbox sees its mail, one person owns each thread, and the team talks about a thread in internal notes that are never sent. It replaces the group address that copies every email into every inbox, where nobody can tell who is answering.

![Mail with the Hello shared mailbox: the thread list on the left and a prospective customer's email open in the middle, with its two attachments, a teammate's internal note asking Maya Chen to reply, and a suggested reply written by the Content Writer agent waiting to be used.](https://volobox.io/docs/images/mail-thread.light.webp)

*A shared mailbox in Mail: the thread list with its views, an email with two attachments, a teammate's internal note, and a suggested reply marked Draft · not sent.*

## How Mail connects to your email

Each address is a **shared mailbox**. Volobox reads it through a **mailbox account**: a Google Workspace account an administrator connects for this purpose, which receives the shared address's mail. Replies go out from the shared address.

Volobox is not a mail client. There are no folders or labels, and nobody's own inbox is read. Volobox changes nothing in Gmail: it only sends the emails people write in Volobox.

Only the people added to a mailbox read its mail, as **Member** or **Manager**.

> **Note:** Permission to set up Mail does not show any mail, including to administrators.

## Threads with one owner

A **thread** is one exchange with somebody outside, with a reference like `SALES-142`. It has one owner or none, and a status: **Open** (the team owes something), **Waiting on them** or **Done**.

A reply moves a thread to **Waiting on them**, and a new email from the other side opens it again, so nothing has to be cleared by hand. Views split the mailbox into **Unassigned**, **Mine**, **Waiting**, **Done** and **All**. A mailbox can hand new mail out to its people in turn instead of leaving it unassigned.

The owner gets a **Mail waiting on you** card in the Inbox while the team owes a reply. If mail sits without an owner for too long, the mailbox's managers get an alert. See [Dashboards and alerts](/docs/dashboards-and-alerts).

## Replies and internal notes

The box under a thread writes two different things, and they look different on purpose:

- An **internal note** stays in Volobox, and only your team reads it.
- A **reply** is an email, sent from the shared address under the mailbox's name and signature.

**New email** starts a thread with someone who has not written yet.

Volobox sends no automatic answers and no acknowledgements. An email leaves only when a person selects the send button.

## Working as a team

- **Follow** a thread you do not own to hear when something happens on it.
- **Share** one thread with a colleague outside the mailbox, who can read it and add notes but not reply.
- See when a colleague **is replying**, so two people do not answer at once.
- Create a **task** or a **request** from a thread, which links back to it. See [Projects](/docs/projects).
- Paste a thread's reference into a chat, task or page. A reference gives nobody access.

While **Screen sharing mode** is on, senders, subjects and email text are hidden.

## Assistants and workflows

AI reaches a mailbox only when its **AI may read this mailbox** setting is on. It is off by default.

With it on, each new thread gets a short AI summary and a suggested owner. The AI pass never assigns a thread and never sends anything.

Your own assistant can then, in your direct chat with it, list and read the mailbox's threads, leave an internal note, save a **suggested reply**, and assign or finish a thread after you approve its card. A personal workflow can start when new mail arrives, or when a thread changes owner, is answered or is marked done.

> **Note: No assistant, agent or workflow ever sends an email**
>
> A suggested reply is a draft marked **Draft · not sent**. A person in the mailbox selects **Use as reply**, edits it and sends it as their own.

Mail is never read in a team channel, a shared chat or a shared workflow, and mail events never leave Volobox through webhooks or apps.

## Related

- [Home and Inbox](/docs/home-and-inbox)
- [Support](/docs/support)
- [Agents](/docs/agents)
- [Workflows](/docs/workflows)
- [Integrations](/docs/integrations)
