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

# Email inbox

> A shared inbox for customer email, and the accounts your sequences send from.

Recepta.ai handles email in two distinct roles. Keep them separate in your head — they use different accounts for good reasons.

<Columns cols={2}>
  <Card title="Shared inbox" icon="inbox">
    Customer email arriving at your normal business address, threaded per contact so your team can work it alongside calls and texts.
  </Card>

  <Card title="Sequence sending" icon="paper-plane">
    Outbound email from [sequences](/outbound/sequences), sent from dedicated infrastructure so cold volume never touches your main domain.
  </Card>
</Columns>

## Connecting an inbox

Under **Settings → Email accounts**, connect the mailbox your customers already write to. Messages appear as conversations linked to the matching [contact](/outbound/contacts), so the whole history — call, text, email — sits in one place.

<Note>
  Connecting your inbox does not change how your email is delivered. Recepta.ai reads and sends through the account you connect; your existing mail setup is untouched.
</Note>

## Why sequences send from somewhere else

Cold outbound and transactional business email have opposite deliverability profiles. Sending campaign volume from the domain you use for invoices and customer replies risks your reputation on the mail your business actually depends on.

Recepta.ai keeps them apart: sequences send from separate [sending domains and mailboxes](/outbound/email-infrastructure), warmed independently.

<Warning>
  Don't point sequence sending at your primary business domain. A deliverability problem there means your quotes and invoices stop arriving — far more expensive than a slow campaign.
</Warning>

## Unsubscribes

Every sequence email carries an unsubscribe link. Opt-outs are honored automatically and permanently — the address is suppressed across all future sends, from sequences and from the API alike.

<Warning>
  Never re-import a suppressed address to work around an opt-out. It's a CAN-SPAM violation and it damages the sending reputation of every other campaign on that domain.
</Warning>

## Templates

Reusable email templates live under **Email templates** and can be used as sequence steps or sent individually. Personalize with contact fields so a template reads as a message rather than a mailshot.

<Card title="Email infrastructure" icon="server" href="/outbound/email-infrastructure">
  Sending domains, mailboxes, warmup, and the deliverability rules that keep campaigns landing.
</Card>