Original Message:
Sent: 05-27-2026 07:48
From: Marudhu Pandian
Subject: Campaign/Agentless Email Domains
Hi All,
Irrespective of whether you use our native solution for outbound email campaigns or use your own SMTP server instead, we strongly recommend using a dedicated subdomain to isolate campaign traffic and protect the deliverability of critical business or transactional emails. Here is a link to the best practices to follow if you are using your own SMTP server for outbound email campaigns, which is DIG-I-1265 referred to in one the responses above: https://help.genesys.cloud/articles/best-practices-to-use-your-smtp-server-to-run-email-campaigns-and-send-agentless-email-notifications/.
Though you could create one outbound campaign domain in GC with the same name as your root domain, we do not recommend it for the reason stated above. Hope this helps.
Thanks,
------------------------------
Marudhu Pandian
Genesys - Employees
------------------------------
Original Message:
Sent: 05-21-2026 02:46
From: Matthew Tipler
Subject: Campaign/Agentless Email Domains
Anyone from Genesys able to provide clarity on this please?
Regards.
------------------------------
Matthew Tipler
Original Message:
Sent: 05-20-2026 04:31
From: Matthew Tipler
Subject: Campaign/Agentless Email Domains
Aghhhhh, thanks for sharing this - that's really helpful.
If I'm understanding correctly, this enhancement appears to have removed the requirement to use a subdomain when configuring Campaign/Agentless Email with a custom SMTP integration.
However, my question is specifically around Campaign/Agentless domains using the Genesys native email service rather than a custom SMTP server.
Historically, the documentation stated that Campaign/Agentless domains should always be subdomains because of the SparkPost configuration and associated CNAME requirements.
In my environment, I've now been able to create and provision a root domain (mydomain.net) as a Campaign/Agentless domain using the Genesys native email service and Genesys generated the expected TXT/CNAME verification records without issue.
I'd like to understand whether root domains are now officially supported for Campaign/Agentless domains using the Genesys native email service as well, or does the November 2025 enhancement only apply to SMTP-backed Campaign/Agentless configurations?
In short:
- Campaign/Agentless + SMTP = Root domains now supported? (appears to be yes)
- Campaign/Agentless + Genesys native email (SparkPost) = Are root domains now supported here too (I can create them within the org)?
Hope that makes sense!
Thanks.
------------------------------
Matthew Tipler
Original Message:
Sent: 05-20-2026 03:53
From: Stephan Taljaard
Subject: Campaign/Agentless Email Domains
Hi Matthew
Apologies, think I had a typo in the link - https://genesyscloud.ideas.aha.io/ideas/DIG-I-1265
Regards
------------------------------
Stephan Taljaard
EMBEDIT s.r.o
Original Message:
Sent: 05-20-2026 03:47
From: Matthew Tipler
Subject: Campaign/Agentless Email Domains
Hi Stephan,
Thank you for your response!
Although https://genesyscloud.ideas.aha.io/ideas/DIG-I-1265. =

I cannot see any release notes within https://help.genesys.cloud/release-notes/genesys-cloud/november-10-2025/ that relate to use of sub or root domains within campaign/agentless configurations.
Regards.
------------------------------
Matthew Tipler
Original Message:
Sent: 05-20-2026 03:30
From: Stephan Taljaard
Subject: Campaign/Agentless Email Domains
Hi Matthew
I found this on the Aha Ideas portal - https://genesyscloud.ideas.aha.io/ideas/DIG-I-1265.
It refers to a feature that was enabled on 23 January 2026 - https://help.genesys.cloud/release-notes/genesys-cloud/november-10-2025/

Regards
------------------------------
Stephan Taljaard
EMBEDIT s.r.o