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

# Inbox

> Read and reply to email alongside the records it belongs to.

**Inbox** is the email half of the [CRM](/guides/crm) section, reached from the CRM
disclosure in the sidebar. The two live together on purpose: they're the same subject
from two angles — who your team deals with, and what was said to them.

<Frame caption="The Inbox, alongside the CRM it writes into.">
  <img src="https://mintcdn.com/open-hive/1xpysC1e-PlVBDLW/images/inbox.png?fit=max&auto=format&n=1xpysC1e-PlVBDLW&q=85&s=b1803e38f486ac6a6ee6f09898f93c2c" alt="The Inbox, alongside the CRM it writes into." width="1440" height="900" data-path="images/inbox.png" />
</Frame>

<Note>
  Inbox is feature-gated and may not be enabled on your workspace. When it's off, the
  CRM section shows records only, and reply controls explain that email senders need
  turning on first.
</Note>

## Conversations

The Inbox lists conversations across every connected mailbox. Search across them, or
filter by kind to separate outreach replies from everything else.

A newly connected mailbox fills in as it syncs, so an empty list right after adding one
is expected rather than a failure.

<Tip>
  Opening a thread in OpenHive never marks it read or sends a read receipt on the
  original platform. You can review what an agent received without the sender seeing
  that you looked.
</Tip>

## Replying

Open a thread and write a reply. The composer supports CC and BCC, file and image
attachments, and placing an image inline in the body at your cursor.

You can also **describe the message you want** and have a model draft it for you, rather
than writing from scratch — useful for working through a batch of replies quickly.

OpenHive guards the obvious mistakes: if a thread was already answered, it tells you and
asks you to reload rather than sending a duplicate, and a sender that can't carry
attachments says so instead of silently dropping the files.

## Sending profiles

A **sending profile** is the identity attached to an account — the name and signature
that go on every email it sends. Set these up before your first campaign; they're what
recipients actually see.

The signature editor has a live preview, so you can check how it renders before it goes
out on real mail.

## Mailboxes and senders

See [Email senders](/configuration/senders) for connecting mailboxes, choosing a
provider, and controlling send volume.

## The mail bridge

Incoming mail is matched to CRM records and written through, so a reply appears against
the person who sent it. Correspondents that couldn't be matched to a record are listed
separately, so nothing gets silently dropped on the floor.