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

# The agent's email address

> Find your agent's address, bring it into a thread, and optionally give it an address on your own domain.

Every organization's agent has an email address. It is how work gets from your mailbox into Casa Conect without anyone copying and pasting.

## Find the address

Go to **Settings → Agent inbox**. Under **Agent address** you see the **Primary address** and, if you have set up your own domain, the original address under **Also reachable here**. Both keep working.

The default address is built from your organization's name, in the form `your-office@agent.casaconect.ai`. The Inbox's empty state also shows it, with a button to copy it.

## Bring the agent into a thread

> Share this address with your team; forwarding or CC'ing a thread invites the agent into it.

<CardGroup cols={3}>
  <Card title="Forward" icon="forward">
    Forward a client's email to the agent with a line saying what you want: *"File the attachments and draft a reply asking for the missing NIE."*
  </Card>

  <Card title="Copy in" icon="users">
    Add the agent in CC on a thread. It follows along and picks up its part.
  </Card>

  <Card title="Let clients write directly" icon="mail">
    If you allow client domains, clients can email the agent themselves. See [Sender rules](/inbox/sender-rules).
  </Card>
</CardGroup>

What the agent is allowed to do depends on who is writing. A verified member of your organization gets the agent's full working abilities. An allowed external sender gets triage only: the agent reads, files and drafts, and never takes instructions from the message. See [Sender rules](/inbox/sender-rules#what-each-kind-of-sender-can-do).

## Use your own domain

Admins can give the agent an address on a domain you control, such as `agent@ai.your-firm.es`, so that clients see your name rather than ours.

<Warning>
  Use a dedicated **subdomain**, never your main domain. Receiving mail requires an MX record, and changing the MX record of your main domain would reroute all of your existing email. Casa Conect rejects apex domains for this reason.

  If you would rather not delegate a subdomain, create a forwarding alias in your own mail system instead, for example `agent@your-firm.es` forwarding to your agent's Casa Conect address.
</Warning>

<Steps>
  <Step title="Add the domain">
    Under **Settings → Agent inbox → Your own domain**, enter the subdomain, for example `ai.your-firm.es`.
  </Step>

  <Step title="Create the DNS records">
    Casa Conect shows the records to create at your DNS provider: three DKIM `CNAME` records for signing, an `MX` record so the subdomain receives mail, a `MAIL FROM` `MX` record with an SPF `TXT` record for bounce handling, and a DMARC `TXT` record. Copy them exactly.
  </Step>

  <Step title="Wait for verification">
    Casa Conect re-checks the records every couple of minutes and shows progress as *"3 of 6 verified"*. Choose **Check now** to check immediately. When every record is found, the domain becomes **Active** and the new address becomes the primary one.
  </Step>
</Steps>

<AccordionGroup>
  <Accordion title="Verification expired">
    If the records are not found within 72 hours, verification expires. Choose **Restart verification** to get fresh records, then update your DNS.
  </Accordion>

  <Accordion title="That domain is already connected to another organization">
    A domain can be connected to one organization only. If you believe this is a mistake, [contact support](/get-started/get-help).
  </Accordion>

  <Accordion title="Removing a domain">
    Admins can remove a domain at any time. The agent's original `agent.casaconect.ai` address continues to work throughout.
  </Accordion>
</AccordionGroup>

## Addresses that are never assigned

Common role names such as `postmaster`, `abuse`, `admin`, `support`, `info`, `security` and `noreply` are reserved and can never become an agent address. This prevents an agent from receiving mail that was meant for a person in charge of a mail system.