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

# Email channel setup

> Connect a sending domain, create addresses, and set assistant email defaults

Email is a workspace channel like WhatsApp or the web widget: connect a domain once, create one or more sending addresses on it, and assign each address to an assistant. Configure it under **Settings → Channels → Email**.

<Note>
  Only workspace owners and admins can configure the email channel.
</Note>

## Connect a domain

<Steps>
  <Step title="Add your domain">
    Enter a domain or subdomain — a subdomain such as `mail.your-domain.com` is recommended, so your main domain's existing mail setup is untouched.
  </Step>

  <Step title="Add the DNS records">
    At your DNS provider, add the three CNAME records (one for sending, two for authentication) and the one MX record shown for the domain. Copy buttons avoid typos, and each record shows its own status as it's picked up.
  </Step>

  <Step title="Verify">
    Click **Verify DNS**. Propagation can take a few minutes — if verification fails right away, wait and try again.
  </Step>
</Steps>

A domain must be verified before you can create an address on it.

## Create addresses

Once a domain is verified, create one or more addresses on it — for example `support@mail.your-domain.com` — and assign each to an assistant. One assistant answers a given address at a time; create another address on the same domain to give a second assistant its own inbox. An address can carry its own sender name, overriding the workspace default below.

## Default sender name and signature

Set a workspace-wide **Default Display Name** and **Default Signature**. Both apply to any address that doesn't set its own sender name, and to the built-in **Send email** tool when it's configured to use the workspace default. The signature supports an `{agent_name}` placeholder, replaced with the sending assistant's name at send time, so one signature template works across every assistant.

## Billing

Sending and receiving email costs credits per message, at the workspace's **Send email** / **Receive email** rate. Current rates are on the [Usage page](https://app.famulor.io/usage); see also [How usage is billed](/billing/minutes).

## History

Every email conversation — inbound and outbound — appears in [Email history](/email/history), grouped into one conversation per exchange the same way a call groups into one row.

## API & MCP

* REST: `GET`/`POST /api/v1/email/domains`, `GET`/`DELETE /api/v1/email/domains/{id}`, `POST /api/v1/email/domains/{id}/verify`, `GET`/`POST /api/v1/email/addresses`, `PATCH`/`DELETE /api/v1/email/addresses/{id}`, `GET`/`PUT /api/v1/email/settings` (`assistants:read`/`assistants:write`)
* MCP: `list_email_domains`, `connect_email_domain`, `get_email_domain`, `verify_email_domain`, `delete_email_domain`, `list_email_addresses`, `create_email_address`, `update_email_address`, `delete_email_address`, `get_email_settings`, `update_email_settings`

See also [Email history](/email/history), [Messaging channels](/channels/messaging), [How usage is billed](/billing/minutes).