Domains

The Domains screen lists every hostname your organization uses with AgentStack. Hostnames are grouped, so one hostname is one card, however many things it does. Each card holds one row for each use: email sending, email receiving, an agent's embed widget, an agent's help page, or an agent's help center. AgentStack also issues two hostnames of its own — the mail host that auto-generated agent addresses sit on, and the free help center address every site gets. Those rows are read-only and link to the agent that owns them.

What each row tells you

A row shows the use, its status, and the agent it belongs to. An email domain belongs to the whole organization, so it names no agent. A web domain belongs to one agent.

Each kind of use keeps its own status words. A web domain reads Waiting for DNS, Verifying DNS, Provisioning SSL, Active, DNS failed, SSL failed, Removing, or Suspended. Email receiving reads Waiting for MX or Active. Email sending reads Waiting for DNS, Verified, or DNS failed. Do not compare a status on one row with a status on another kind of row.

Open DNS records on any row to see the records that use needs. Every name is written in full, so you can copy it into your DNS provider without working out whether the provider wants a label or a full host. Click a value to copy it.

Add a domain

Select Add domain, then select what the hostname is for.

An email domain lets your agents send from your own address, and can also receive. Use a subdomain such as mail.acme.com: receiving needs a subdomain, and a subdomain keeps your main domain's mail untouched. Email domains are available on paid plans, and an organization can hold three.

Domains used to be added from an agent, on /org/[slug]/agent/[id]/channels/email/domains/add. That route still answers, and it sends you here with the email form already open, so an old bookmark keeps working.

A web domain serves one agent's widget, help page, or help center. Select the agent, then enter a subdomain such as support.acme.com. Web domains come from the Custom Domain add-on, not from a plan tier. The counter at the top of the page counts every agent's web domains together, because the limit applies to the whole organization.

One hostname cannot do two of these

A hostname that receives email publishes an MX record at that exact name. A web domain needs a CNAME at the same name, and DNS does not allow a CNAME to sit beside any other record. So one hostname can serve the web, or receive email, but not both. AgentStack refuses the second one before it changes anything, and tells you which record is in the way.

Email sending is different. Its records sit at child names, so a domain that only sends can share a hostname with a web domain.

If a hostname was set up both ways before this rule existed, the card shows a warning. Remove the web domain, or turn receiving off, and the warning clears.

Verify, change, and remove

Check DNS asks the provider to look at your records again and updates the status. Verify MX does the same for receiving.

Routes to changes which surface a web domain serves. If the domain is live, AgentStack asks you to confirm, because visitors see the change immediately.

Remove on a web domain takes it offline at once. Remove on an email domain removes it for every agent in the organization, along with every address on it. Disable receiving stops inbound mail but keeps sending and keeps the addresses. After you disable receiving, delete the MX record for that hostname at your DNS provider. AgentStack cannot delete records in your zone. An MX record that still points at AgentStack with receiving off delivers mail nowhere.

Every action needs the channels:configure permission. With channels:view alone you can read this page but not change anything.