Which Atender surfaces can have custom domains?
Short answer: the Knowledge Base portal and the Status page. Everything else either uses a default Atender URL or has its own separate configuration path. Here’s the full map.
Surfaces that go through Custom Domains
These are the only two products you can manage from Settings → Custom Domains.
- Knowledge Base portal —
help.example.com,support.example.com,docs.example.com - Status page —
status.example.com,health.example.com,uptime.example.com
Pick the product when you add the domain. Each entry binds to one product.
Surfaces that don’t go through Custom Domains
The other places where Atender content shows up are configured separately or aren’t customizable at the domain level today.
Agent app login URL
The Atender agent UI — the screens your team works in — runs at the standard Atender tenant URL. You can’t currently swap that for your own domain like app.example.com. Customers don’t see this URL; only your agents do, so the branding payoff is small.
Web Chat widget
The Web Chat widget loads from Atender’s domain via a script embed. The widget UI shown to the customer can be re-branded (logo, primary color, opening message) inside the widget’s own settings, but the underlying script URL doesn’t accept a custom domain. Configure widget branding under Settings → Channels → Web Chat → (your widget) → branding.
Email sending domain
When Atender sends email on your behalf — replies from your agents, automation-triggered emails, CSAT surveys — those go out from an email domain you configure separately. That setup involves SPF, DKIM, and MX records and lives under the email channel configuration, not Custom Domains. See the channels-email docs for that flow.
Public Incidents embed widgets
The status page itself can run on a custom domain (via Custom Domains, as covered above). But the embed snippets generated on the Incidents Embed tab — the script and iframe you paste into your marketing site — reference the default Atender host by default. You can manually replace the host in those snippets with your custom status hostname after the domain is Active.
CSAT surveys
CSAT survey landing pages run at Atender’s default URL. There’s no custom domain mapping for the survey response page today.
Outbound transactional emails
Welcome emails, password resets, and other Atender platform-level emails go from Atender’s transactional sender. There’s no per-tenant override for these.
Why not the agent app?
The agent app and the customer-facing surfaces are different products with different needs. Custom Domains exists to put your brand in front of customers — both the help center and status page are pages your customers visit, so a branded URL is high-value there. The agent app is internal-facing; agents are logged in and don’t need a branded URL to trust where they are.
If you have a legitimate reason for needing the agent app on a custom domain (e.g. some enterprise security requirement), reach out to Atender support to discuss. It’s not a self-serve setting.
Can I add the same root domain to multiple products?
Yes — within the same tenant, you can have help.example.com mapped to the Knowledge Base and status.example.com mapped to the Status page, both running off example.com. See Help and Status on the same base domain for the parallel setup.
Can I add the same hostname to multiple tenants?
No. A hostname maps to a single tenant. If you try to add help.example.com to a tenant when it’s already connected to another tenant, the second add will fail. This is also true across environments — production and development tenants are different tenants, even if they belong to the same company.