Email domains
Where email domains are added and verified now, and what the old per-agent add route does.
An email domain belongs to the whole organization, not to one agent. Every agent in the organization can send from a verified domain, and removing a domain removes it for all of them. So domains are added, verified, and removed in one place: the Domains screen, under Workspace → Domains. The old per-agent route /org/[slug]/agent/[id]/channels/email/domains/add still works. It redirects to the Domains screen with the add form already open, so an old bookmark or an old link keeps working.
Add a domain
On the Domains screen, select Add domain, keep the use set to Email, and enter the domain you control. AgentStack registers the domain for sending and shows the DNS records it needs. Add those exact values at your DNS provider. Do not use guessed values for SPF, DKIM, or MX. A mail provider can change the records it requires, so always copy the values the dashboard shows for your domain.
The records table shows a Priority column when a record needs one. The MX record for receiving mail is the usual case. Copy that number into the priority field at your DNS provider. Do not put it in front of the host name in the value field.
Then select Check DNS on the sending row. DNS changes take time to propagate. A correct record at your registrar does not mean that mail delivery is ready. Adding an email domain needs a paid plan and the Channels: configure permission.
Sending and receiving are separate
Sending and receiving are verified separately, and each keeps its own status. Sending reads Waiting for DNS, Verified, or DNS failed. Receiving reads Off, Waiting for MX, or Active. A domain that sends does not receive until you select Enable receiving, add the MX record shown, and verify it.
Receiving publishes an MX record at the hostname itself, so that hostname cannot also serve a web surface. AgentStack refuses the pair rather than letting it fail silently. See Domains for what a conflict looks like and how to resolve it.
While a record is missing or still propagating, keep the email channel disabled or use the managed AgentStack address.
After the domain is verified
Add a local address in Channels → Email, on the agent that should own it, and choose the verified domain. Email addresses stay with the agent; only the domain is organization-wide. Test inbound and outbound mail with a safe address. Before you route customer traffic to the new domain, review the returned message, the rate-limit behavior, and the alert contact.